Start from the source
Connect a public or private GitHub repository, select a branch, and choose the application directory. Review detected settings before the first build.
Take your application from a Git repository to a public URL. Openstead builds and runs your code, connects your domain, and brings each deployment’s logs into one place.
Your code. Infrastructure included.
WEB SERVICES ON OPENSTEAD
Keep the framework, commands and repository you already use. Give every application a home with its own configuration and resources.
Connect a public or private GitHub repository, select a branch, and choose the application directory. Review detected settings before the first build.
Deploy manually or enable automatic deployments for your connected branch. Build output, commit details and release status stay together.
Connect your domain using the DNS records shown in the console. Track verification and certificate status without leaving your service.
MADE FOR YOUR STACK
Openstead supports common application runtimes including Node.js, Python, PHP, Go, Java, Ruby and Rust. Keep detected commands or use a Dockerfile for full control over your build.
Repository your-team / application
Branch main
Runtime Python
Build pip install -r requirements.txt
Start gunicorn config.wsgi:application
--bind 0.0.0.0:$PORT
Health check /health/Use the module and health endpoint from your application. Build and start commands are editable.
PUT IT TO WORK
Server-rendered Next.js, Django and Laravel applications with a persistent backend.
HTTP services that connect your clients to application logic, databases and background jobs.
Applications with native dependencies or a specialized runtime, packaged with your own Dockerfile.
HOW IT WORKS
Select a repository and branch. Set the root directory for a monorepo, review detected commands, and add environment variables.
Choose an instance, configure a health check, and deploy. Follow the build and startup stages as Openstead prepares your service.
Add a custom domain, follow application logs and inspect resource usage. Deploy your next change from the same service.
No. Openstead provides and operates the hosting infrastructure. Bring your application repository or container image and the configuration it needs to run.
Yes. Free web instances are available with defined resource and usage allowances. They sleep when idle. Choose a paid instance for an always-running application and features such as persistent disks.
Treat the application container as replaceable. Store durable uploads on an attached persistent disk or in external object storage. Persistent disks require a paid application instance.
Yes. Create the app and database in the same environment and configure the app with the database’s private connection details. Each service has its own resources and plan.
MAKE YOUR NEXT MOVE
Your code. Infrastructure included.