Everything worth asking before you trust a platform with production.

A European application deployment platform. Connect a Git repository and DebutDeploy builds it, runs it in an isolated container, issues TLS, and gives you logs, metrics, health checks, rollbacks and managed Postgres — at a fixed monthly price per service.

The workflow is deliberately similar; the commercial model is not. Transfer is 20 TB included rather than metered, team seats are free rather than per-user, and equivalent compute is 29–51% cheaper depending on plan. Compute runs in Germany and Finland only.

Railway meters vCPU, memory and egress by usage, so the monthly figure is only knowable afterwards. DebutDeploy sells a fixed box: you choose CPU and memory and pay the same amount every month.

In enterprise-grade data centres in Falkenstein, Germany (fra1) and Helsinki, Finland (hel1), inside the EU. The region is shown on every service.

Yes — DebutDeploy is a control panel and orchestration layer on top of leased enterprise European infrastructure, rather than data centres we own. That is how the pricing works, and the current subprocessors are named in the published subprocessor list.

It is operated by Debut Web Consultants, a UK company, and it runs the products that company builds and operates. Full registered company details are in the site footer.

Yes. Every application and database runs in its own container with its own resource boundaries. Plans at 2 vCPU and above run on dedicated CPU that is not shared with other tenants.

Yes. Deploy from a Dockerfile in your repository, including multi-stage builds and private base images.

Node.js, Python, Go, Ruby, PHP and static frameworks are detected and built automatically. Anything else deploys via a Dockerfile.

Yes, as their own always-resident services with their own CPU and memory. They do not sleep between jobs.

Yes. Jobs run on a cron expression per service, with output in the same log view as your deploys.

Unlimited custom domains, with TLS certificates issued and renewed automatically via Traefik. There is no charge for certificates and no plaintext endpoints.

Not yet. Preview environments per pull request are planned and are not available today — if that is central to your workflow, it is a genuine gap.

Yes. PostgreSQL 16 instances from $5/mo, provisioned in the same panel, with the connection string injected into your service as an encrypted environment variable.

Nightly, at 03:00 UTC.

Seven days by default. Longer retention and point-in-time recovery are available on request rather than as a published plan feature.

Yes. Your code stays in your own Git repository and you can take a full pg_dump of any managed database at any time. There is no proprietary layer to unpick if you leave.

Yes. Persistent disks can be attached to services that need state which outlives a deploy.

20 TB of outbound transfer per month on every plan — HTTP responses, API traffic and media delivery all count against the same allowance.

We contact you to agree a plan. There is no automatic overage charge applied to your card.

No per-GB egress fee inside the included allowance. This is the line that most often makes usage-based platforms unpredictable.

Monthly via Stripe, in USD or GBP. No contract, no minimum term, cancel any time.

No — prices are shown excluding VAT. VAT is applied at checkout where applicable, based on your billing country.

Yes. Team members are included at no extra cost, and agency or multi-service portfolios are quoted under a Custom plan rather than forced into single-app tiers.

Yes. Assisted migration reviews your services, databases, variables, volumes, domains and workers, reproduces them here, validates the result and prepares a rollback plan before any traffic moves.

Usually none for the cutover: we reproduce and validate the service, then move DNS. Databases with large datasets need a short agreed write-freeze window. Your existing service stays online throughout preparation.

Yes, and it is the recommended route. Run the same repository here alongside your current provider for a billing cycle before deciding anything.

Email support with next-business-day response on all plans, and migration support from an engineer rather than a ticket queue. Faster response commitments are part of Custom arrangements.

An SLA document is published and forms part of the terms. Any specific availability commitment beyond it — including credits and carve-outs — is agreed in writing under a Custom arrangement rather than implied.

Yes. Programmatic API tokens are scoped read-only or full, revocable, and enforce per-resource ownership checks.

On the live status page at status.debutdepoly.com, which is also where incidents are published while they are being investigated.

Sign in with GitHub or Google. Repository access uses a single read-only deploy key, requesting only the GitHub scopes needed to build and deploy.

No. Security controls are designed around industry-standard practices, and certifications will be published only once they are genuinely held.