Overview#

The Midnight marketing site is the public product site for deployatmidnight.com. It describes the self-hosted Midnight alpha — the topology workspace, staged environment changes, deployment evidence, project administration, usage evidence, and the dashboard, CLI and API surfaces — and it is the only place those claims are published to a general audience.

It is a small, server-rendered site: one page, a set of metadata routes, and a worker that adds security headers and a canonical-hostname redirect. There is no content management system, no editor, and no user accounts. Changing what the site says means changing source and deploying it.

Who operates it#

One maintainer. The site is deployed to a Railway service and served from the apex hostname deployatmidnight.com; requests to www.deployatmidnight.com are redirected to the apex.

What it is not#

The marketing site is not the Midnight product. It does not run deployments, hold control-plane state, or talk to a Midnight installation. It describes Midnight; it does not operate it. The two are separate repositories with separate deployments, and a change to one never requires a change to the other.

It also holds no customer data. The database layer is wired but the schema is deliberately empty, so nothing is stored per visitor.

The claim boundary that matters#

The site presents an alpha honestly, and its test suite enforces that. The production-build test asserts that specific phrases are present in the rendered HTML, and that a specific set of retired claims is absent. If you reintroduce a claim the product cannot support, the build fails rather than publishing it.

That makes the test the authority on what the site is allowed to say. Read Verifying a change before editing copy.

Where to go next#

• Local setup — get the site running on your machine.
• Editing page content — change the published copy.
• Deploying — publish to production and confirm it.
• Troubleshooting — when a build, assertion or redirect misbehaves.