PlatformServerless deploy

Serverless deploy

Apps that scale on their own — from marketplace to runtime.

In Deploy, developers run their own apps on the eQuantic Cloud as serverless services that scale automatically, including to zero when idle.

Create a service

The wizard is a marketplace by category. The Custom category (default) covers four sources:

app.equantic.space/deploy/gateway
gatewayLiveGit
api.equantic.space
CPU
MEM
autoscaling · 1–6 instances
1Autoscaling
Every service scales on its own (including to zero) — CPU, memory and instances visible at a glance.
SourceWhat it does
Git repositoryWe detect the stack, build the Dockerfile and discover the port and variables — auto-detect.
DockerfileBuild from a Dockerfile in the repository.
Docker ComposeBrings up multiple services from a compose.yml.
Docker imageUses a ready-made image from a registry.

The other categories bring ~40 ready-made open-source services (Postgres, Redis, RabbitMQ, MinIO, Grafana, n8n, Metabase, Keycloak, WordPress…), each with its own installation form.

Operate the service

  • Overview with CPU/memory charts and source/build.
  • Deployments with a live build stream and rollback.
  • Scale & resources — scale triggers (KEDA), scale-to-zero, instance range, and CPU/memory editable at any time — resizing a running service rolls it forward with the new share, no recreate.
  • Health check — point the platform at your app's own probe endpoint, and override the container's command/args when the image's defaults aren't yours.
  • Interactive Console (drawer), live runtime logs, variables and domains (automatic TLS).
  • Advanced configuration (EXPERT) — resource/probe overrides and inspection of the generated manifest.

The wizard's advanced settings carry the same knobs at creation time — resources and instance range chosen there are what the first deployment runs with.

Open Pull Requests can also get ephemeral preview environments, deployed like regular services and destroyed automatically on merge/close — see Repositories & CI/CD.

The platform does not expose servers/nodes — it's serverless. Each project is an isolated environment and each service scales by instances.