Public status
The public boundary, stated plainly.
This page distinguishes what is serving today from what is reserved or still being prepared. Private operations and evidence stay inside authenticated surfaces.
Current release posture
What is public now—and what is not.
These labels describe the current product boundary. They are not inferred from private infrastructure, internal runs, approvals, or deployment activity.
Public website
OperationalThe company website, contact paths, and this release-posture page are serving.
Customer app
Pre-productionapp.droco.io is reserved. A dedicated authenticated product shell is not live yet.
Public API
Pre-productionapi.droco.io is reserved. The reviewed API contract remains repo-only until its edge gate passes.
Public identity
Pre-productionauth.droco.io is reserved. Private Authentik access remains the current identity boundary.
Public availability
The website exposes a minimal liveness path at /status/droco. Independent uptime and incident reporting will replace this release-posture view before customer-facing production is declared.
Private by default
Run evidence, approvals, deployment history, capacity, topology, operator details, and incident internals stay behind authenticated product and operator boundaries.
Public by design
Public pages explain customer-visible availability and product readiness without turning internal operations into marketing content.
Private by default
Internal service names, LAN hostnames, allocation details, capacity totals, paths, secrets, customer data, and incident notes stay behind authenticated operator tools.
Evidence governed
Proof remains a product capability. Runtime evidence is disclosed only to authorized people, customers, and auditors in the proper context.