Deploy a web app from the Git branch that you connect, with the build steps for the framework that Runtime detects. Runtime deploys every later push and scales the app with its traffic, down to zero instances while the app is idle.
To detect the framework, Runtime parses the config files in the branch that you connect, and then it deploys the build to a live URL. After the deploy, Runtime scales the app with its request traffic and serves it over TLS on its .conjoin.app subdomain and on any custom domain that you add.
Connect a repository on GitHub, GitLab, or Bitbucket and choose the branch to deploy. Runtime redeploys the app each time you push a commit to that branch.
Runtime identifies the framework from your package.json, requirements.txt, or equivalent file. For each framework that Runtime detects, it chooses the build and start commands itself, so you can leave the build configuration out of your repository.
Runtime sets the number of instances from your app's request traffic, adding instances as traffic increases and removing them as it falls, so you have no scaling rules to write.
While an app has no traffic, Runtime keeps it at zero instances, so Conjoin bills no compute for it. When traffic resumes, Runtime serves the first request after a cold start of under 500ms.
Once you add a domain and point its DNS records at the app, Runtime provisions a TLS certificate for that domain. Every app also has a default subdomain on .conjoin.app.
Runtime starts each new version alongside the current one and moves traffic to it once the new version passes its health checks. To roll back, make one API call that names any earlier deployment.
Runtime starts each new version alongside the current one and moves traffic to it once the new version passes its health checks. To roll back, make one API call that names any earlier deployment.
From zero instances to serving the first request
Detected from the files in your project
Moves traffic back to any earlier deployment
When you deploy the dashboard's repository, Runtime returns a .conjoin.app URL for it. From then on, Runtime builds every push, scales the dashboard with its traffic, and serves it on any custom domain that you point at it.
The repository is the only part of the dashboard that you maintain, since Runtime performs the builds and the scaling and issues the TLS certificate.
Deploy the staging branch with scale-to-zero enabled. Runtime scales the environment down to zero instances once QA traffic stops and starts an instance again when a developer next opens the URL.
Conjoin bills compute for the staging environment only while an instance serves requests, so the hours between QA rounds add no compute charge.
Push an app whose framework appears on the supported list. At deploy time, Runtime selects the build command and start script for that framework from your project files.
Runtime builds and starts the app from its code and package manifest, so you have no deployment file to write for each framework.
During a deploy, the current version serves every request until the new version passes its health checks, after which Runtime moves traffic over.
When a new build crashes on start, Runtime keeps sending your users to the current version, so you have no emergency rollback to perform.
Conjoin will open with a free Build tier, while the pricing page already lists the launch prices for Pro and Business. If you tell us what you're building, we'll talk you through early access.