Deploy the code you own
Connect a repository and branch, review the build and start commands, then set the runtime port and health check. Static sites and web services have different operating needs.
MolternFounders
For your team
Ship the first version. Keep a way forward.
Turn your repository or agent-built prototype into an application with data, services and a URL you can share.
Flight paths artwork / 02
The demo works on your laptop. Now a customer needs to try it. Start with one application and the services it actually needs. Keep configuration, deployment history and ownership together so the next version does not become an infrastructure project.
Put it into practice
Connect data privately
Put the service in the appropriate environment and use explicit private connections where supported. Keep server credentials out of browser code and source control.
Check the release people will use
Inspect deployment status and logs, verify the URL and test the application’s main workflow. Record who owns configuration changes, service upgrades and recovery.
Detailed instructions are maintained in the product documentation.
Questions before you start
Can I keep my existing framework?
Use a supported runtime or a Dockerfile. Review the application guide for your build output and server requirements.
Who owns backups and recovery?
Name an owner and review the service-specific persistence and recovery instructions before relying on its data.
What should I check when a deployment fails?
Start with deployment logs, build commands, runtime port, health checks and required variables, then follow the troubleshooting guide.
Keep exploring
All pages ↗
Start with one useful workload.
Bring your code or choose a service, then give the result a clear operating home.
Start building ↗