Early access
Request early access.
We are opening comOS up one capability at a time, starting with the path from a repository to a running deployment. Leave your email and we will send an invite when there is one.
Early access starts with the part that works.
We are opening up one capability at a time, starting with getting an application from a repository to a running, observable deployment. The resource types around it come after that, not alongside it.
- Deploy from GitConnect GitHub or GitLab, review the detected build plan, then ship. Every build logs live and every deployment is listed with a rollback.current
- Runtime controlSet environment variables, mark secrets for encryption, attach custom domains, and size the resource while it is running.current
- Managed resourcesPostgreSQL, Redis, functions, queues and object storage are being built. They are not available yet, and we would rather say so than take a sign-up for them.building
Frequently answered questions
The short version of what early access is, and what it is not yet.
How do invitations work?
One at a time, in the order people joined. We do not have a batch or cohort system, so there is no cohort to wait for — you get an email when we have an invite for you.
What does early access include?
Applications only: deploying from Git, live build logs, environment variables and encrypted secrets, custom domains, and deployment history with rollback. There is nothing to pay for and nothing to install.
What is not ready yet?
Managed PostgreSQL, Redis, functions, queues and object storage are still being built. They are marked as in progress on our features page, and we would rather you hear it here first than discover it after you have planned around it.
What do I need to bring?
A Git repository. comOS reads it, works out how to build it, and shows you the plan for your review before anything is deployed, so you can correct it if it guesses wrong.