🚀 Four new cloud services are live in beta.

Since September 1, 2026, we have opened Edge, Compute, Container and Runner to a closed beta — available to existing customers only — while we tune them in the real world 🎉

This is the part of the work we have been quietest about, and it is the part we are most pleased with. For years the answer to "where do I put this?" was a cPanel account or a VPS, and both are good answers for a lot of things and the wrong answer for a Next.js front end, a queue worker, or a nightly import. So we built the four shapes that were missing, on infrastructure we operate ourselves.

⚡ What each one is for

Four services, and the honest way to choose between them is what your workload actually does between requests.

⚡ Edge — static sites and server-rendered front ends. Connect a repository and push. Your framework is detected, built, and served from a container that is already running, which is why there is no cold start on the first visit of the day. Next.js, Nuxt, Astro, React, Vue, Svelte and plain static output all work. See what Edge does →

🧮 Compute — reserved capacity for steady workloads. A machine of your own, billed by the hour for what it reserves, always warm. For an API that holds connections, a worker that cannot miss a tick, or anything keeping state in memory. See what Compute does →

📦 Container — bring your own image, we run it. Built from your repository or your own Dockerfile, billed by the second while it runs, and asleep when nothing is asking. For bursty work: internal tools, webhook receivers, nightly imports, staging environments nobody opens at the weekend. See what Container does →

🔧 Runner — jobs, builds, and scheduled work. A managed always-on service with no disk to size and no host to log into. You push code; we keep it available, probe it, patch it and renew its certificates. See what Runner does →

💡 What you get on all four

The platform is the same underneath, so the operational parts do not change when you move between services 🛠️

  • Git-push deploys — connect a repository, pick a branch, and every push builds and ships. No pipeline to write, no runner to maintain.
  • Live build logs — streamed while the build runs, so a failure is something you read rather than something you guess at.
  • Metrics and alerting — memory, CPU, disk and traffic, with alerts that fire before a ceiling becomes an outage.
  • Instant rollback — moving an alias, not rebuilding. Undoing a bad deploy is a click.
  • Custom domains — with TLS issued and renewed by us. Nothing expires on a Friday night.
  • Managed data services — PostgreSQL, MySQL, MongoDB and Redis, one hop from your application on the same network.

And the part we care about most: you do not need to know any devops to use it. The machine, the container engine, the reverse proxy, the certificates, the database, the backups and the monitoring are ours. If you can push to Git, that is the whole skill set.

🔒 Why the beta is closed

Because "it works on our servers" is not the same claim as "it works on yours", and the gap between those two is exactly what a beta is for 🙂

We run our own eight production sites on this platform, which is a real test and a narrow one — eight applications we wrote, deployed the way we deploy things. What we do not have is your repository, your build quirks, your traffic shape, or the framework version you are pinned to for a reason. That is what the beta is buying us.

So it is existing customers only, in small numbers, with us watching. No public sign-up, no credit card, no "start free" button — there is nothing to sign up to yet, and we would rather say that plainly than collect email addresses for a thing that is not finished.

🙏 Thank you

Huge thanks to the customers testing with us right now. You have already found things we would not have — a build template that assumed too much, a log line that said the wrong thing at the wrong moment, a metric that was technically correct and completely unhelpful. Your feedback is shaping what ships next, and several of the fixes are already live 💚

📣 What happens next

We are tuning against real workloads, closing what the beta surfaces, and writing down the parts that are still rough. When general availability is ready, we will announce it here and email everyone on the platform — you will not have to check back.

General availability is coming soon. In the meantime:

Thanks for reading, and thanks for building things with us 🚀

— Md. Ashraful Alam Shemul