Open-source PaaS · self-hosted first

Deploy to your own server— without building your own platform.

Midnight brings builds, releases, routes, logs, health, and rollback to a Linux VM you control. Keep your compute and data on your terms, with one control plane for the CLI and dashboard.

Prefer a managed option? Tell us what you would need from Midnight Cloud.

License
Apache-2.0
Starting point
One Linux VM
Current release
Alpha preview
Self-hosted software
$0
Serviceapi-production
healthy
releaser_01J8F2
replicas1 / 1
route statepublished
rollbackavailable
deployment timeline
18:42:11 source accepted
18:42:15 image digest pinned
18:42:19 replica healthy
18:42:20 route published
YOUR INFRASTRUCTURE ONE CONTROL PLANE DURABLE RELEASE HISTORY NO PER-SEAT SELF-HOSTED FEE

The platform

The deployment workflow, on infrastructure you choose.

Hosted platforms trade infrastructure control for convenience. Midnight brings the operational workflow to your server, then keeps the important state understandable when something fails.

01Build and release

From source to a durable release

Deploy local source or a connected repository. Midnight records the operation, image, rollout, and result so the next move is visible.

02Routes and domains

Know what is ready before traffic moves

Generated routes, custom domains, DNS ownership, and certificate readiness live beside the service—not in a separate pile of ingress config.

03Operations

Health, logs, and recovery in one place

Inspect deployments, follow logs, restart safely, and roll back with the release history still attached to the service.

04One control plane

CLI and dashboard stay in step

Use the interface that fits the moment. Both paths operate on the same projects, services, environments, and deployment timeline.

Developer workflow

Three commands. One visible deployment.

Link a directory to a service, ship it, and follow the same operation from the terminal or the dashboard.

  • Local source packaging honors your ignore rules.
  • Every trigger creates a trackable operation.
  • Release and runtime state stay attached to the service.
midnight / your-app
$ midnight login
session saved for operator@example.com

$ midnight link
linked production / api

$ midnight up
source accepted · operation queued
midnight-01 online
control planeworkerbuildkit registrytraefikyour services
one trusted Linux VMscale out when the product is ready for it

Single VM first

Start with the server you already know.

Midnight is designed around one trusted Linux VM today. The control plane, build path, registry, ingress, and workloads stay explicit—without asking you to become a Kubernetes operator.

Alpha software: evaluate it on infrastructure you can recover. Production hardening and multi-host runtime work are ongoing.

Choose your operating model

Control when you want it. Convenience when you need it.

Self-hosting is available now. A managed service is something we are exploring with operators who want the workflow without running the control plane themselves.

AVAILABLE NOW · ALPHA

Midnight Self-Hosted

Apache-2.0 software for your VM. You control compute, data, networking, upgrades, and recovery.

  • Open source and forkable
  • No per-seat software fee
  • Built around one VM first
Self-host Midnight
EXPLORING

Managed Midnight

The same product workflow, operated for teams that would rather spend their time on applications than platform maintenance.

  • No launch date or pricing claim yet
  • Shaped with real operator feedback
  • Self-hosted remains a first-class path
Tell us what you need

Questions

Know what Midnight is—and what it is not.

Is Midnight production-ready?

Not yet. Midnight is an alpha preview for evaluation on a trusted Linux VM. The project is actively hardening deployment, recovery, domains, and certificate evidence.

Does Midnight include hosting?

The available edition is self-hosted software: you bring the server and network. A managed edition is being explored, but it is not a product commitment today.

Does it configure HTTPS automatically?

Midnight models routes, domains, DNS ownership, and certificate readiness. Public HTTPS still depends on a reachable origin and correctly configured DNS and certificate automation.

Why one VM?

One clear host is easier to install, understand, back up, and recover. Midnight is building multi-host foundations without pretending that runtime is finished today.

Deploy at Midnight

Your server. Your applications. One calmer control plane.

Start with the open-source alpha today—or help shape the managed path you would actually pay for.