Sign in, link GitHub, choose a repository
Everything downstream — analysis, the assistant, and deployment — works on the one repository and branch you pick here. Set it once; it follows you through every step.
1 Sign in
Authenticate to the control plane. Your session is stored locally in this browser.
Account security
2 Connect GitHub
Validated against GitHub, then stored encrypted. Only the last 4 characters are ever shown back.
3 Choose the working repository
Pick the repo and branch the rest of the app should operate on.
AI codebase analysis
Produce an architecture, API surface, data-model, user-journey, and security review for the working repository — grounding everything you do next.
Select a working repository in Step 1 · Connect to analyze it.
Analyze
Reads a high-signal digest of the repository and returns a structured report.
Engineering assistant
Hold a multi-turn conversation with a full-stack developer, system architect, or security specialist — optionally grounded in your working repository.
Sign in at Step 1 · Connect to use the assistant.
New conversation
Conversations
No conversation selected
Start or select a conversation.
Namecheap deployment console
Create a production target for your working repository, ship it, tail live logs, and roll back. Secrets stay in cPanel or GitHub Actions.
Sign in at Step 1 · Connect to manage deployments.
Launch a hosted app or client variant
Hosts the working repository on a subdomain of one of your domains in one step: creates the subdomain, registers the app, requests HTTPS, wires the repository and ships the first release. Launch the same repository again under another name to give a client their own copy. Every push to the branch then updates each copy.
No launch yet.
Hosted apps & client variants
App settings ·
Values are stored encrypted and never shown again; only names are listed. Saving updates the copy's GitHub secret; tick "apply now" to redeploy with the change.
Current settings: —
Create deployment target
Repository & branch are taken from your working context.
Targets
Configure automatic deployment
This submits the integration files and deployment secrets to the selected GitHub repository. Future pushes to its configured branch trigger deployment. For Python/Node runtimes the Passenger application is registered automatically when the subdomain is created; request HTTPS afterwards via AutoSSL.
Deployment runs
Push or merge into the configured production branch → GitHub Actions builds → SSH uploads → release activates → health check. Changes become visible after a successful deployment; other branches do not update production.
Live log
No run selected.Projects
Create a starter, inspect its files and choose it when configuring a deployment target. Creating a project saves its source manifest here; it does not push source to GitHub.
Create project manifest
Your projects
Project files
Hosting & domains
Map your parent domains and app subdomains to your Namecheap account. Each app needs its own target and release directory.
Account configuration
Parent domains
An administrator configures the account's parent domains on the server. DNS must point each app hostname to its hosting server.
HTTPS certificates
Every website on the account gets a free Let's Encrypt certificate as soon as its name reaches this server, and is renewed 30 days before expiry. No AutoSSL needed.
Runtime setup
Setup checklist
Existing cPanel subdomains
Platform tools
Runtime status, project manifests, direct AI execution, code generation, provider links, and payment lifecycle — the lower-level building blocks.
Runtime status
AI execution
Generate code
Provider link
Your provider links
Sign in to load provider links.
Payment
Payment history
Sign in to load payments.