Project X

Secure deployment for applications built with AI

Take a dashboard, prototype or site created in an AI coding environment and put it into production without learning containers, CI or cloud infrastructure. Project X scans the artifact, tells you what it found, hosts it, and keeps every version immutable and reversible.

Start deploying Sign in

Scanned before it ships

Hardcoded credentials, unsafe install hooks, native binaries and malicious patterns are detected during import. Secret values are never displayed — only the file and line where they were found.

Immutable versions, instant rollback

Every import creates an immutable version. Production is a pointer you can move back to any healthy deployment — no rebuild, no drift.

Tenant isolation by construction

Knowing a resource identifier is never enough. Every read and write is scoped to your workspace, and every privileged action is written to an audit trail.

Write-only secrets

Application credentials are encrypted at rest and can be created, replaced and deleted — but never revealed. There is no API that returns a secret value.

Import without Git

Bring an artifact straight from an AI coding environment as a bundle, a paste, or a base64 payload through the API. Git is supported but never required.

API-first

Everything the dashboard does is available over a documented REST API with scoped, revocable tokens, so agents and CI can drive deployments.

What this deployment hosts

Stated plainly, because a deployment platform that overstates its scope wastes your time:

Supported Static applications and pre-built bundles — anything that already contains a servable index.html or a built dist/, build/ or public/ directory. This covers the large majority of artifacts produced by AI coding environments.
Not supported Server-side runtimes (Node, Express, FastAPI, Streamlit) and artifacts that require a build step such as npm install and next build. Imported source projects are analysed and their findings reported, but they are not compiled here.
Hosting address Deployments are served on platform paths rather than per-project subdomains, because the connected Cloudflare account has no DNS zones. Custom domains are recorded but not routable on this deployment.