Queued is not live
A deployment or build that is queued, requested or building is displayed in exactly that state. Nothing is shown as published before it is.
Status
This page asks the platform health endpoint on this origin whether the web runtime is answering, and shows exactly what came back. It does not claim monitoring that does not exist.
Checking
Asking the health endpoint on this origin for its status.
The health route deliberately reads no configuration, database or provider state, so it can never leak or depend on secrets. That also means it can only ever tell you that the web runtime is up.
The state of each part of the platform right now.
| Area | State | Note |
|---|---|---|
| Website and dashboard | Live | hostingsurge.com, the customer dashboard and the health endpoint checked above. |
| Platform API, CLI and MCP | Live | REST API under /api/v1, the hostingsurge CLI and the MCP server at /mcp with OAuth sign-in for AI clients. |
| Deployments and hosting | Live | Git push-to-deploy, uploads and Docker images, build and runtime logs, rollback, environment variables, cron jobs and deploy hooks. |
| Domains and SSL | Live | Custom domains with ownership verification, the exact DNS records to add, automatic certificates and redirects. |
| Databases | Live | PostgreSQL, MySQL, MariaDB, Redis and MongoDB with scheduled backups and restore. |
| WordPress | Live | Managed sites with updates, hardening, health checks and backups. |
| Imports and migrations | Live | Vercel, Netlify, any Git host, WordPress backups, cPanel, SFTP/FTP, database dumps and website snapshots, each checked on a preview URL. |
| Live | Mailboxes, aliases and IMAP import; transactional sending is enabled per organization after review. | |
| AI builder | Early access | Rolling out to accounts step by step. |
| Billing | Implemented, not live | The credit ledger, verified top-ups and subscription fulfillment are implemented. No price catalog is published yet, so no purchase can be completed. |
| Branch previews, deployment protection, uptime checks and notifications | In development | Being added now; they appear in the dashboard when they ship. |
A few rules the platform applies everywhere — they are the reason some states look different from a marketing page.
A deployment or build that is queued, requested or building is displayed in exactly that state. Nothing is shown as published before it is.
When a provider key or connection is missing, the platform says not_configured and stops. It does not invent a result or retry forever.
A failed build or run records the failure and its category. A build artifact receipt exists only after the bytes have been hashed, stored and read back.
There is no uptime percentage, incident history or customer count on this page, because none of those exist yet to report.
The docs show where every feature lives in the dashboard and the CLI; the developers page covers the API.
There is no uptime history, incident feed, SLA or third-party probe behind this page. Those are in development, and this page will link them when they exist.