Enterprise

The platform you never outgrow.

Start small on the beta. Our direction is to grow to dedicated servers, then to your own cluster, without rewriting a deploy script or moving to another cloud: the same deplane deploy, the same dashboard and the same API at every size. Dedicated servers and the steps after them are on the roadmap, not available today.

The problem

Why growing teams leave their platform.

Heroku, Vercel, Render and Railway are great at the start. Then a company grows, and the same three reasons push it onto AWS, where it rebuilds everything a platform used to do for it.

Cost

The bill outgrows the value

Platforms that rent their servers from AWS or Google pay that margin and pass it on. At scale, running it yourself starts to look cheaper, even with the extra engineers.

Compliance

Shared isn't allowed anymore

A bank, a hospital or a government customer asks where the data lives and who else runs on the same machine. "A shared region in someone else's cloud" stops being an acceptable answer.

Control

No say over the hardware

Dedicated machines, a private link to existing systems, a chosen data center: a software-only platform can't sell what it doesn't own.

Never outgrow Deplane

Five steps. One platform.

Deplane runs in its own data centers. When you need more than shared servers, we don't send you to another provider: we give you more of ours. Every step keeps your apps, commands and workflows exactly as they are.

01 · Start

Shared, isolated

Shared servers, every instance in its own microVM. GitHub deploys, Postgres, domains, alerts. Live in minutes. Available today in the beta.

Beta today · Pro $15 soon
02 · Team

More of everything

Planned: unlimited apps, 8 GB running, 3 databases, 10 members, activity log, a 99.9% SLA and priority support. Coming soon.

Team · $99 · soon
03 · Scale

Dedicated servers

Servers that run only your apps, inside our cluster. Moving there is meant to be a placement setting we change for you, not a migration. Roadmap

Enterprise
04 · Big

Your own cluster

A cluster or region of your own on bare-metal servers, with its own private network and compliance controls. We run it. 2027

Enterprise
05 · Largest

Private Deplane

The whole platform inside your own account or data center, still upgraded and operated by us. 2027

Enterprise

Why we can promise this: Vercel, Render and Railway run on AWS and Google Cloud, so "your own infrastructure" is not theirs to offer. We own the data centers, the servers and the network under Deplane. Today only step 1 exists, as the free beta on shared servers. Step 2 is coming soon. Steps 3, 4 and 5 are on the roadmap, with 4 and 5 targeted for 2027.

What you get

Built for the questions your security team will ask.

Dedicated servers Roadmap

Not available yet. The plan: your apps, builds and databases run on machines used by no other customer, and every workload still gets its own microVM. Size the servers to your load, and add more without changing anything in your apps.

Data residency in Europe

Deplane runs in our own data centers in Europe, not on a US hyperscaler. Choosing the region your data lives in is on the roadmap.

Compliance paperwork

A data processing agreement (DPA), audit log export, and our security controls in writing, as part of Enterprise contracts. SOC 2 and ISO 27001 · 2027

Single sign-on

SAML and OIDC sign-in, SCIM provisioning, and roles for viewers, developers, admins and billing. Q2 2027

Private networking

A private link between your Deplane apps and your existing servers and databases, with no public internet in between. Q2 2027

99.95% SLA and a named engineer Roadmap

What we plan to offer Enterprise customers: a person who knows your setup, a shared channel with our team, and response times written into the contract.

Procurement that fits

Invoices instead of a card, local currency and invoicing, annual contracts and volume pricing for compute, databases and support.

Migration

We move your apps with you.

Coming from Heroku, Render, Vercel, Fly.io or your own servers? Our engineers plan the move with your team, deploy each app on Deplane next to the old one, and switch traffic when you are ready.

  • No rewrite. Deplane builds the same code without config. A Dockerfile works as is.
  • Databases copied and checked before anything switches over.
  • DNS last. Both versions run side by side until you move the domain.
Migration planacme
shop (Next.js) deployed on Deplane, testedDone
api (Django) and 2 workers deployedDone
Postgres 42 GB copied, checking row countsRunning
Move shop.acme.com and api.acme.comThu 06:00
Turn off the old platformNext week
How it works

From first call to production.

01 · Call

Tell us what you run

A 30-minute call with an engineer, not a sales script: your apps, your data, your rules. We come back with a setup and a price.

02 · Pilot

Try it in a pilot

A pilot with one or two real apps on the beta platform. Servers reserved for you are on the roadmap. Your team uses the CLI, the dashboard and GitHub deploys for real.

03 · Production

Migrate and go live

We move the rest with you, then you run in production under the SLA, with your named engineer on hand.

Contact sales

Let's talk about what you need.

Tell us about your apps, your team and any rules you work under, and what you would need from dedicated servers. An engineer answers.

  • Prefer email? Write to sales@deplane.cloud.
  • Security questionnaire? Send it along. We fill them in.
  • Already running servers elsewhere? Mention it, and we can connect Deplane to what you run today.

We use your details only to answer you.

Start small. Stay as you grow.

Begin with one app in the free beta. The ladder above is the direction we are building toward.