#Getting Started
CoDuck is an AI-powered platform where you describe what you want to build in plain English and get a live, deployed full-stack app. Every project comes with hosting, a dedicated Postgres database, custom domains, email sending, Stripe payments, file storage, and automatic backups — all configured for you.
#Start a project
- Sign up at coduck.ai/signup (or sign in at coduck.ai/login).
- On the home page, you'll see a prompt textarea with a rotating placeholder showing examples like "Generate an online store for selling handmade products."
- Type what you want to build and hit enter.
CoDuck's AI scaffolds the codebase, generates the UI and backend, and deploys it. The project opens at https://app.coduck.ai/project/<projectId> with a chat-based editor where you can keep iterating.
#What you can build
One project gives you one container, one Postgres database, and one .coduck.app subdomain. From there:
| Capability | What you get | Docs |
|---|---|---|
| Bring your own code | Import an existing Next.js, React, or Node project | /docs/projects/create-existing |
| Deploying | Zero-downtime redeploys with auto SSL | /docs/projects/deploy |
| Custom domains | Point your own domain with one-step DNS verification | /docs/domains/custom-domains |
| Database | A dedicated Postgres database per project | /docs/database/overview |
| Sending email | Transactional email from your own verified domain | /docs/email/sending |
| Stripe payments | Stripe Connect — payouts go directly to your account | /docs/payments/stripe-connect |
#Manage your project
Open https://app.coduck.ai/project/<id> and you'll see three things side by side: the chat, the code editor, and the Cloud panel.
The Cloud panel has the following tabs:
| Tab | What it controls |
|---|---|
| Settings | Project name, framework, general config |
| Hosting | Sub-tabs: Domains, Env, Deploys, API Key |
| Analytics | Built-in traffic and event analytics |
| Data | Your project's Postgres database — schema, rows, queries |
| Logs | Live deploy and runtime logs |
| Forms | Form submissions captured from your site |
| Transactional email, verified domains, send history | |
| Payments | Stripe Connect status and payouts |
| Activity | Audit trail of changes to the project |
To make changes, either edit through the chat (ask the AI to add a feature, change a layout, wire up a new endpoint) or use the Cloud panel for infrastructure-level controls.
#For developers and AI agents
CoDuck also ships a CLI (@coduckai/cli) for bringing existing code into the platform, scripting deploys, and letting AI coding assistants drive CoDuck end-to-end. The calling assistant should remain the coder: it edits and tests the repository itself, then uses CoDuck for sync, previews, infrastructure, and deployment. CoDuck's own agent commands are available for deliberate special cases, not as the default coding path. See /docs/cli/install to get set up.
#For AI agents reading these docs
If you're an AI assistant working with CoDuck on a user's behalf, fetch one of these at session start for full fluency across every feature:
- /llms.txt — index of every doc with one-line summaries
- /llms-full.txt — every doc concatenated into a single file
When the user asks you to build or change code, implement and verify it yourself by default. Do not automatically delegate it through coduck chat, coduck ask, or coduck generate; those commands invoke a separate CoDuck project agent. Use them only when the user explicitly asks for that agent or another deliberate exception applies.