Deployment

Ship your project to the world from the workspace publish flow. Use Codeezly CDN for built-in hosting, or connect Vercel and Netlify when you want launches to run in your own hosting account.

Deployment Targets

Codeezly CDN

Publish static projects to Codeezly CDN without connecting an external hosting account.

1. Click Publish in the workspace toolbar to open the publish panel.
2. Select Codeezly as the deployment target.
3. Run the security and build checks, then publish.
4. Share the generated /sites/<slug> URL.

Vercel

Deploy to your connected Vercel account for production-grade hosting with edge functions and analytics.

1. Click Publish in the workspace toolbar to open the publish panel.
2. Connect your Vercel account if it is not already configured.
3. Select your Vercel team and project (or create a new one).
4. Click Deploy. Vercel builds and deploys your app in your connected account.

Features: Serverless functions, edge network, preview deployments on branches, automatic rollback, and Vercel Analytics.

Netlify

Deploy to your connected Netlify account for JAMstack hosting with forms, identity, and functions.

1. Click Publish in the workspace toolbar to open the publish panel.
2. Connect your Netlify account if it is not already configured.
3. Select your Netlify team and site (or create a new one).
4. Click Deploy. Netlify publishes the site in your connected account.

Custom Domains

Deployment targets support custom domains from the publish panel:

1. Click Publish in the workspace toolbar and switch to the Domains tab.
2. Add your domain name (e.g., www.example.com).
3. Add the provided DNS records (CNAME or A record) to your domain registrar.
4. SSL is provisioned automatically by your deployment provider once DNS propagates.

Continuous Deployment

When connected to GitHub, every push to your main branch triggers an automatic deployment:

• Push code → build starts automatically.
• Pull request branches get preview deployments.
• Merge to main → production deployment.

See the Version Control guide for setting up GitHub integration.

Environment Variables

You can set environment variables for your deployment:

1. Click Publish in the workspace toolbar.
2. Switch to the Env Vars tab.
3. Add key-value pairs (e.g., NEXT_PUBLIC_API_URL, DATABASE_URL).
4. Variables are encrypted at rest and injected at build time.

Tip: Use different values for development and production by setting environment-specific overrides.

AI Assistant & Credits

Apps that include the built-in chat AI call Codeezly's AI gateway. There is no API key to obtain by default — the platform runs the model and bills usage to your Codeezly credits. Each message costs a small amount, so keep a credit balance for the assistant to keep working. You stay in control from Publish → AI:

• Turn it off. The chat AI is on by default for apps that requested it. Toggle it off any time to remove the assistant and guarantee no AI credits are ever spent.
• Cap monthly spend. Set an optional ceiling on this app's monthly Codeezly-credit AI spend so a viral or abused app can't drain your balance.
• See usage. The panel shows how much this app has spent on AI this month.

Bring your own provider key

To pay your AI provider directly instead of spending Codeezly credits — recommended when you deploy outside Codeezly — add any one of these in the Env Vars tab:

• ANTHROPIC_API_KEY
• OPENAI_API_KEY
• GOOGLE_API_KEY

When a provider key is present, the gateway uses it and your provider bills you directly — no Codeezly credits are used. Keys are encrypted at rest and never exposed to your app's visitors.

Deploying outside Codeezly? The chat AI still works: requests route back to Codeezly and bill your Codeezly credits unless you set your own provider key, and the same on/off switch and spend cap apply. Turn AI off before export if you don't want it to consume credits.

Rollbacks

Every deployment creates a snapshot. To rollback:

1. Click Publish in the workspace toolbar.
2. Switch to the History tab.
3. Find the deployment you want to revert to.
4. Click Rollback. The previous version is live instantly.

Troubleshooting