Two surfaces, different jobs
MinuteWork gives developers two distinct surfaces:
- the private Server runtime for private payloads, authenticated behavior, installed capabilities, and payload-aware execution
- the published web surface for intentionally public traffic, previews, custom domains, and publication-safe releases
Both belong to the same product, but they solve different problems and should not be blurred together.
Private runtime
The private runtime is the default home for:
- documents, transcripts, drafts, and private workflow data
- authenticated app behavior
- installed packs and tenant-specific logic
- payload-aware AI execution
- secrets and privileged integrations
If a feature depends on private tenant state, approvals, or authenticated operator workflows, it probably belongs in the Server runtime.
Published web
The published web surface is for things a Server intentionally exposes to anonymous or external traffic, such as:
- marketing pages
- docs sites
- blogs and public knowledge bases
- customer-facing portals that need a public entry point
- preview and live releases behind domains or path prefixes
Published web is not just "read the runtime from the browser." It has its own release and hosting model so anonymous traffic does not require a private runtime to stay awake by default.
Preview versus live
Preview and live have different trust levels.
Preview can stay close to the runtime and may reflect unpublished or draft-safe content. It is for validation, review, and pre-publication iteration.
A practical decision rule
Use this shortcut when deciding where something belongs:
- Private runtime when the feature handles drafts, private payload, authenticated operator work, or tenant-local automation
- Published web when the feature must serve anonymous users, SEO pages, or public reference content
- Both when you need a private authoring or operator surface plus a public published result
That last case is common. A team may manage content privately inside the Server runtime, then publish a release-safe version to a public docs or marketing site.
Why this matters for developers
This split keeps the architecture honest:
- private payload does not leak into a shared public host
- anonymous public traffic does not force a runtime wake by default
- publication becomes an explicit act with releases and receipts
- local development can still test preview behavior without pretending preview and live are the same thing