Start from source, an image, GitHub, or a template
Create services, attach storage, deploy digest-pinned images, package local source, connect an approved repository, or launch an official database template from one project workspace.
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. Shape environments in a topology workspace, review changes before applying them, and keep your compute and data on your terms across the dashboard, CLI, and API.
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
f0c132c with deterministic .test data. It contains no customer data and is not presented as live-backend proof.The platform
A project workspace for the whole deployment lifecycle.
Hosted platforms trade infrastructure control for convenience. Midnight brings resource creation, environment topology, configuration review, deployment evidence, and administration to your server—then keeps the important state understandable when something fails.
See each environment as a saved system map
Switch between grid and topology views, arrange real services and explicit attachments, and keep the layout versioned without confusing presentation with runtime health.
Stage environment changes without pretending they deployed
Keep a durable, encrypted draft of variable changes, review redacted intent, validate it, and apply it atomically. Deployment and restart remain separate, explicit actions.
Deployments, logs, metrics, routes, and recovery stay attached
Follow the Operations Tray, inspect canonical deployment history, stream build evidence, manage domains, restart safely, and roll back without losing the release trail.
People and automation use explicit authority
Manage workspace and project members, invitations, project-scoped automation tokens, GitHub links, variables, and webhook evidence without silently falling back to recovery access.
Dashboard, CLI, API, and usage evidence stay in step
Use the interface that fits the moment, backed by the same scoped resources. In-app guides cover agent setup, the API contract, and the CLI; usage stays labeled by source and completeness.
Product tour
Inspect the workflow before you install it.
Use the tabs for a guided walkthrough, then inspect full console captures from the same deterministic journey. The capture uses real Midnight routes and components with synthetic .test data.
Midnight consolerepresentative data
acme / storefrontproduction healthy
Environment resources
production
See services, storage, and observed runtime state in the same environment view.
AapiWeb service
Healthy- Release
- 9c4e2ab
- CPU
- 12%
DBpostgresDatabase template
Healthy- Storage
- 2.4 GB
- CPU
- 4%
Guided rendering of the current product interface. Names and values are representative; no production customer data is shown.
Captured September 21, 2026 from commit f0c132c. These assets prove the console workflow and rendering; installed-host claims remain in the evidence record below.
Candid comparison
A Railway-like workflow with a different operating model.
Midnight brings the core application workflow to infrastructure you run. Hosted infrastructure remains Railway's advantage; control and inspectable evidence are Midnight's focus.
On a narrow screen, scroll the table horizontally to compare every column.
| Capability | Midnight today | What that means | Railway model |
|---|---|---|---|
| Projects, environments, and services | Available | Create and operate resources from the console, CLI, or API. | Hosted workspace |
| Source and immutable image deploys | Available | Local source, digest-pinned images, release history, and rollback. | Hosted builders |
| Logs, metrics, health, and audit | Available | Service-scoped evidence with explicit degraded and unavailable states. | Managed observability |
| GitHub source integration | Operator configured | Requires a Midnight GitHub App and repository grants. | Managed integration |
| Custom domains and public HTTPS | Operator configured | Requires reachable ingress, DNS, and certificate automation. | Managed edge |
| Off-host backup and recovery | Operator configured | Requires an S3-compatible destination and a tested restore path. | Managed service options |
| Automatic preview environments | Operator configured | The workflow is implemented; installed private-GitHub evidence remains open. | Available |
| Multi-region, autoscaling, and HA | Planned | Today Midnight deliberately targets one trusted Linux VM. | Hosted infrastructure |
Status describes the current self-hosted alpha. Operator configured means the feature needs infrastructure or credentials that Midnight cannot truthfully assume.
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. No parallel system of mystery scripts.
- Local source packaging honors your ignore rules.
- Every trigger creates a trackable operation.
- Release and runtime state stay attached to the service.
$ midnight login
session saved for operator@example.com
$ midnight link
linked production / api
$ midnight up
source accepted · operation queuedcontrol planeworkerbuildkitregistrytraefikyour services
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.
Proof, with boundaries
Follow the evidence behind the claims.
Product status should be inspectable. These links point to retained reports and the exact verification paths in the public repositories—including the work that still needs a complete run.
Fresh install and source-to-HTTP deploy
The dated readiness record names the exact install and DocVault checks that passed, and names the public HTTPS and recovery checks they do not prove.
Read the readiness recordMarketing site HTTPS and deployment path
The checked-in runbook documents the systemd service, Caddy ingress, canonical redirect, and the probes an operator must run after deployment.
Inspect the site runbookPackage install and doctor checks
The operator path defines the package artifacts, service checks, doctor report, first-admin claim, and handoff evidence required on a host.
Inspect the install gatePublic app HTTPS, off-host restore, and private GitHub
These workflows are implemented or operator-configurable, but their complete installed acceptance evidence is still open. Midnight does not present them here as universal proof.
See the required next runChoose 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
- Dashboard, CLI, API, and in-app guides
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
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.
Which Railway-like features are available today?
Projects, environments, services, saved topology layouts, staged variable changes, image and source deploys, approved GitHub sources, official templates, volumes, domains, deployment history, logs, metrics, members, invitations, automation tokens, usage evidence, and in-app API and CLI documentation are available in the current control plane. Automatic preview environments are implemented and require an operator-configured GitHub App; complete installed private-repo evidence remains open. Functions, buckets, project deletion, and enforced host volume quotas remain explicitly unavailable.
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.