Marketing website
Home, hosting (overview, Java, Bedrock, software), features, pricing, about, contact, FAQ and a custom 404 — all responsive and keyboard operable.
Evidence · app/(site)/**, components/site/**
Feature status · four categories
Every capability is labelled by what it actually is.
No feature is described as live because it appears in a mock-up. This page separates software that exists, automation that verifies it, interfaces that simulate an operation, and intentions that are not built.
At a glance
- Available now6
- Tested with automation8
- Simulated — not connected5
- Planned, not built8
Live Minecraft hosting: none. No server is provisioned, no payment is processed, and no customer exists.
This deployment is a static marketing preview. The account system, authenticated dashboard and API described on this page exist in the full application repository but are not included in this export. No account can be created and no server record is shown here.
How to read this page
Four states, no ambiguity.
Available means the software works in this repository. Tested means automated tests exercise it. Simulated means the interface exists but the operation does not. Planned means it is not built.
Available now
Real software in this repository. Accounts and records persist in PostgreSQL when a database is configured.
Tested with automation
Covered by the automated suite. Test counts are reported from the run recorded in docs/WEBSITE_READINESS.md, not estimated.
Simulated — not connected
The interface exists and is honest about it. Buttons are disabled or the panel states plainly that nothing is connected.
Planned, not built
Design intentions only. They depend on infrastructure, security and operations work that has not started.
Available now
Real software in this repository. Accounts and records persist in PostgreSQL when a database is configured.
Accounts and sessions
Email and password registration, login, logout and current-user lookup. Sessions are opaque server-side tokens in HttpOnly cookies.
Evidence · lib/auth/**, app/api/auth/**
Authenticated dashboard
Overview, server list, server detail with real event history, plan comparison and read-only account settings, scoped to the signed-in user.
Evidence · app/dashboard/**, components/dashboard/**
PostgreSQL data layer
Prisma schema, initial migration and plan seed for users, sessions, servers, server events and plans, with database check constraints.
Evidence · prisma/**, lib/servers/**
Policy drafts
Privacy, terms of service and refund/cancellation pages published as clearly marked drafts, so the gaps are reviewable rather than hidden.
Evidence · app/(site)/privacy, /terms, /refund-policy
Baseline browser hardening
CSP, frame denial, MIME-sniff denial, referrer and permissions policy on every route, plus production-only HSTS.
Evidence · lib/security/headers.ts, next.config.ts
Tested with automation
Covered by the automated suite. Test counts are reported from the run recorded in docs/WEBSITE_READINESS.md, not estimated.
Registration and login validation
Strict schemas reject unknown fields, bad email shapes, short or oversized passwords, wrong media types, malformed JSON and bodies over 16 KiB.
Evidence · tests/unit/auth-validation.test.ts, api-validation.test.ts
Password hashing and token storage
Argon2id hashes with unique salts; 256-bit session tokens stored only as SHA-256 hashes.
Evidence · tests/unit/password-tokens.test.ts, session-service.test.ts
Ownership isolation
Every server query is scoped by the session-derived user id; another account's server resolves to 404, not a permission error.
Evidence · tests/unit/server-ownership.test.ts, tests/integration/postgres.test.ts
Session cookie policy
HttpOnly, SameSite=Lax, host-only, server-derived expiry and Secure in production, with logout clearing the cookie.
Evidence · tests/unit/cookie-policy.test.ts
Auth rate limiting
Per-IP and per-email windows with 429 and Retry-After. Single-process and in-memory, so it is not a production control.
Evidence · tests/unit/rate-limit.test.ts, api-validation.test.ts
API error handling
Stable error codes, generic 500 messages, no-store responses and no connection-string leakage.
Evidence · tests/unit/api-errors.test.ts
Security headers
Development and production policies are asserted separately, including HSTS only in production.
Evidence · tests/unit/security-headers.test.ts
HTTP and database integration
Real registration, login, session replay, ownership denial, logout revocation and health checks against a running production build and a local PostgreSQL instance.
Evidence · tests/integration/http-api.test.ts
Simulated — not connected
The interface exists and is honest about it. Buttons are disabled or the panel states plainly that nothing is connected.
Create-server wizard
A three-step preview of the intended flow. It ends by stating that no server was created: there is no POST endpoint and nothing is written.
Evidence · components/dashboard/CreateServerForm.tsx
Power controls
Start, stop and restart buttons are disabled and labelled unconnected. No process or command exists.
Evidence · components/dashboard/ServerCard.tsx, ServerDetail.tsx
Console
Homepage console output is scripted sample text. The dashboard console panel says it is not connected.
Evidence · app/(site)/page.tsx, components/dashboard/ServerDetail.tsx
Resource telemetry
Plan allocations are stored metadata. CPU, RAM, storage and player counts are not measured anywhere.
Evidence · components/dashboard/UsageMeter.tsx
Backups and restores
The backup tab explains that no archive, schedule, storage or restore path exists.
Evidence · components/dashboard/ServerDetail.tsx
Planned, not built
Design intentions only. They depend on infrastructure, security and operations work that has not started.
Minecraft provisioning
Control plane, scheduler, node agent and a per-tenant process or container boundary. Not started.
Evidence · docs/FEATURE_ROADMAP.md
Real lifecycle operations
Start, stop, restart, version changes and graceful shutdown against a real server process. Depends on provisioning.
Evidence · docs/FEATURE_ROADMAP.md
Streaming console
Authenticated command execution, streaming output and an audit trail. Depends on provisioning.
Evidence · docs/FEATURE_ROADMAP.md
Off-node backups and restores
Encrypted object storage, retention policy and a restore path that has actually been drilled.
Evidence · docs/SECURITY_PLAN.md
Payments, invoices and GST
An India-compatible payment provider, webhooks, subscriptions, tax invoices and refunds. No provider is selected.
Evidence · docs/PRICING_SUPPORT_READINESS.md
Email verification and recovery
Verification, password reset and MFA with single-use expiring tokens and a mail provider.
Evidence · docs/KNOWN_LIMITATIONS.md
Support operation
A monitored mailbox, knowledge base, published hours and an escalation path. None operate today.
Evidence · docs/PRICING_SUPPORT_READINESS.md
Additional regions
Mumbai is the planned launch region; Singapore and Frankfurt are later options. No infrastructure exists in any region.
Evidence · docs/AWS_ARCHITECTURE.md
Recurring questions
Three claims we refuse to make.
“Live hosting”
Nothing in this repository provisions a Minecraft server. The dashboard shows records, not running processes, and the console panel says so.
“Enterprise security”
Baseline headers, Argon2id hashing and ownership scoping are implemented and tested. There is no penetration test, no audit log and no production proxy.
“Trusted by”
There are zero customers and zero testimonials. No logo wall, no invented review scores and no customer counter appears anywhere on this site.
Test counts quoted elsewhere on this site come from the last recorded run in docs/WEBSITE_READINESS.md. They are not estimates and are not extrapolated.
Inspect it
The fastest way to judge this is to click through it.
Read the feature status table, compare proposed plans and check the hosting pages. No account is needed and every limitation is labelled in place.
Pre-launch prototype · No live Minecraft server · No payment collected