01
Connect a repository
Choose the project and branch that should deploy.
New service
Static site
Web service
Private service
Workflow
Managed data
A clear path from repository to running service
Deploy apps and services from a repository, with data, previews, logs, and access in one clear path.
$ tupile deploy
SAMPLE SERVICE Ready
tupile-apiPreview
REPOSITORYacme / sample-api
BRANCHmain
Deploy stateRunning
Repository to preview
Start with the repository, shape the service, and see the next environment take form.
02
Configure a service
Set the service type and the environment it belongs to.
main
npm run build
npm start
Preview
03
Review the preview
Check deploy state and open the running service.
~/sample-api$ tupile deploy
Uploading build …
==> Preview is ready
tupile-apiRunning
sample.tupile.dev
Deploy completed
just now
just now
PLATFORM SCOPE
One runtime, connected pieces
From the first commit to the last access decision, Tupile keeps the platform vocabulary in view.
See the platform piecesRepository deploys
Services
Managed data
Previews
Logs
Private networking
Access controls
01 / PREVIEWS
Give every change a place to land
Create a focused preview for a branch before it becomes the next shared release. Review the service path without losing sight of the code that started it.
- Branch-ready previews
- Service state in context
- An explicit path to deploy
PREVIEW ENVIRONMENT
PULL REQUESTfeature / sample-api Checks passed
preview-01
web Ready
api Ready
data Ready
02 / SERVICES + DATA
Keep services and data in step
Run application services beside managed data so the pieces behind a feature stay easy to find. See the relationship between the service layer and the data layer without a second operational surface.
- Application services
- Managed data
- Shared operational view
sample-apiRunning
APPLICATION SERVICEruntime-dataConnected
MANAGED DATA03 / OBSERVABILITY
Follow the story after deploy
See build output, deployment state, and live logs where the service is running. Bring the useful signal closer to the change that caused it.
- Build output
- Deploy state
- Live logs
INFObuild completed
DEPLOYpreview is running
GET/health 200
INFOrequest served
DEPLOY STATERunning
BOUNDARY + ACCESS
Keep the route private. Keep access clear.
Private networking keeps service-to-service traffic on an internal path. Access controls define who can change a service, inspect its state, or move a deploy forward.
Private networking
Keep internal traffic off the public internet without VPC complexity.
Explore private networkingAccess controls
Define who can change a service, inspect its state, or move a deploy forward.
Read the access modelRELEASE EVIDENCE
Check before release
See the build, preview, and access state together.
BUILD CHECKSReady
CompilePassed
TestsPassed
PreviewRunning
PREVIEW ACCESSScoped
Branchfeature/api
EnvironmentPreview
ReviewersTeam
CHANGE RECORDVisible
Commit8f21c4
Deploydp_0142
StateReady
BUILDER SYSTEM
Infrastructure built for builders
Ship a service with the controls that matter.
Native runtimes
Choose the service shape.
Managed data
Keep data beside the service.
Preview environments
Review each branch safely.
Deploy hooks
Connect the release path.
Live logs
Read useful service output.
Background work
Schedule jobs in context.
Private services
Keep internal routes internal.
Custom domains
Attach the public address.
ACCESS + CONTROL
Secure by default
Keep access boundaries visible.
Private networking
Use an internal service path.
Access controls
Choose who can change a deploy.
Environment secrets
Keep configuration out of code.
Audit events
See the latest control change.
Deploy approvals
Hold the release when needed.
Service identity
Give each service its own access.
TUPILE
Start with one service
Connect a repo. Deploy one service.