Connect source
Install the configured GitHub App for selected repositories, or upload a source ZIP.
From source to running application.
Bring your code. Review the detected build and runtime plan. Follow the release through health checks to its HTTPS endpoint.
A visible deployment journey
Know what happens after you press deploy.
Review the plan
Review the framework, build command, start command, port and resource reservation.
Follow progress
Uploading source, storing the snapshot, building, starting and health checking stay visible.
Open the healthy URL
Use the endpoint, read logs, inspect the release ID and return to deployment history.
Application operations · Pilot
Connect configuration, data and recovery.
Configure environments
Import .env entries into encrypted configuration; review Production, Staging and Preview scopes.
Attach managed data
Bind Postgres as DATABASE_URL, Cache as REDIS_URL and project-scoped Store access.
Inspect and query
Open Database Studio for schema, rows and bounded SQL. Write mode requires authorization.
Observe and recover
Review logs, health and rupee usage. Roll back releases or restore database backups through separate workflows.
Implemented source capabilities are offered through controlled Pilot configuration and host validation.
Workload support
Familiar runtimes. Explicit configuration.
Next.jsNode.jsFastAPI / PythonDjangoGoStatic sitesFlutter WebDockerfile applications
These are source-level build paths in the pilot. Detection provides a starting plan, not a guarantee that every repository deploys unchanged. Review commands and test your release.
React / Vite
Use a Dockerfile that builds your app and serves the output directory, or upload built static assets. Package detection alone does not guarantee a Vite production server.
Workers + cron
Background workers belong in the application architecture. General-purpose worker and cron delivery remains a rollout direction; it is not advertised as universally available.
Project configuration
Good defaults. Clear overrides.
Display name + slug
Example: “Client Portal” with slug client-portal. The slug is generated and editable. Changing it does not silently replace a live hostname.
Source hygiene
Keep API keys and private credentials out of Git and source ZIPs. Manage project secrets separately through scoped encrypted storage.
Portable source
Read the deployment guideBring a Dockerfile when you need control.
Custom build or runtime requirements can be expressed in the source. Resource reservations and health checks still apply.
Your next applicationBuild the product.
Build the product.
Keep infrastructure from
becoming the product.
Start with one application. Add data, domains and capacity as it grows.