[data-reveal]{opacity:1!important;transform:none!important}
AntelopeJSCloud

Now availableManaged deployment for your apps

Push code. We run the rest.

Any Docker container is welcome. And if it's an AntelopeJS app, your antelope.config.ts already says what it needs. We read it, provision the databases, wire the secrets, and scale every service, with your maximum bill known before you click deploy.

  • Free tier, protected by a hard cap
  • Scale-to-zero included
  • Any Docker container welcome
  • EU-hosted · dedicated hardware
The platform

Everything after the push, handled.

Kubernetes underneath, none of it in your face. Builds run in the cloud, databases get provisioned, TLS and domains come out of the box, and a console shows you everything that's running, what it costs, and how to roll it back.

Console

Logs, deploys, rollbacks. One pane of glass.

Every service streams its logs live, exposes its metrics, and keeps its full deployment history. The same data is one ajs cloud logs -f away in your terminal.

  • Live log stream with level filters, 30-day retention and log drain on Pro.
  • One-click rollback to any previous build. A new build only replaces the old one if it passes its healthcheck.
  • Per-minute metrics: allocation is what you pay, and you watch it move in real time.

Billing

The scaling ceiling is your maximum bill.

Every app gets a min–max range. Kubernetes scales freely inside it, and the sum of the upper bounds, 24/7, at public rates, is the worst-case number on your invoice. Shown before you deploy.

  • The cap is a promise: on Hobby it stops your apps before your wallet; on Pro we alert and never touch a production without your instruction.
  • What sleeps costs nothing: scale-to-zero, metered by the minute of allocation.
  • No per-seat pricing, ever. Machines, not humans: invite your whole team.

Git connect

Push to deploy. Preview every PR.

Connect the repo and every push deploys, branch to environment. The CLI stays first-class: ajs cloud deploy works from any folder, connected repo or not.

  • Branch → environment mapping: main to production, stage to staging, your call.
  • Ephemeral preview environments per pull request, opt-in, destroyed on merge.
  • Nearly free previews: they scale to zero the moment nobody looks at them.

Also included

The rest of the checklist, already ticked.

Interfaces become infrastructure

Your app declares interface-mongodb? We detect it and provision a MongoDB container on a replicated volume, wired through your existing envOverrides. Zero config drift between laptop and cloud.

Sleeping apps cost nothing

Scale-to-zero is forced on Free and a per-environment toggle everywhere else. Keep production warm, let staging and previews sleep. Host a hundred dormant side-projects; pay only for what actually runs, metered by the minute.

Any container is welcome

Meilisearch, a Python worker, your legacy Express service: add any Docker image to the project. Same network, same volumes, same per-minute billing. AntelopeJS is the golden path, not a cage.

Builds run in the cloud

Shared dependency cache, private registry handled, backend built and started first so the frontend can build against it. No Docker required on your machine.

Zero-downtime by default

A new build only takes traffic once it passes its healthcheck; the old one stays live until then. Roll back to any previous build in one click.

Batteries included, honestly priced

TLS, custom domains, DDoS protection, logs & metrics: included. Volumes at TBD /GB-mo with invisible replication. Egress free up to your plan's allowance, then TBD /GB.

Pricing

A plan, a credit, a cap. Machines, not humans.

Your plan includes a usage credit. Apps pay for what they allocate, by the minute. What sleeps costs nothing, and your spending cap is a hard promise. We never charge per seat: invite your whole team.

Free

TBD/mo

Learn, test, tinker. A cap that protects your wallet.

  • 1 member · 1 project · 3 services
  • 0.25 vCPU / 512 MB max per app
  • 1 GB storage · 20 GB egress
  • Auto-sleep, forced (wakes on first hit)
  • 3-day logs · 1 h build time
Join the community

Hobby

TBD/mo

The serious side-project. Usage credit included (TBD).

  • 1 member · unlimited projects & apps
  • Up to 2 vCPU / 4 GB per app
  • 5 GB storage · 100 GB egress included
  • Spending cap on by default, zero bill shock
  • 7-day logs · daily snapshots · 5 h builds
Join the community
Recommended

Pro

TBD/mo

Startups & agencies. Credit TBD, unlimited team.

  • Unlimited members · unlimited apps
  • Free allocation, min–max bounds per app
  • 20 GB storage · 1 TB egress included
  • 30-day logs + log drain · hourly snapshots
  • Alerts by default, opt-in cap · priority support
Join the community

Enterprise

Let's talk

SLA, compliance, volume, tailored to you.

  • Negotiated volumes & terms
  • Annual billing available
  • Dedicated support
  • Enterprise roadmap: fine-grained RBAC · SSO/SAML · audit logs · dedicated LB · contractual SLA
Contact us

Usage rates:TBD /vCPU-hourTBD /GB(RAM)-hourTBD /GB-mo storage, replication includedTBD /GB egress beyond allowance1 vCPU + 2 GB: TBD /mo, 24/7

The cap is a promise, not a suggestion. On Hobby it stops your apps before your wallet; on Pro we alert and never touch a production without your explicit instruction. On Free, hitting a limit pauses the app behind a friendly upgrade page. Data and volumes always survive.

Get started · Join the community

Your next deployment starts here.

Explore the platform, then join the community on Discord to get started and share feedback with the team.