CozyOps turns conversational messages into deployed, production-grade applications. Describe what you need. Get working code, a live preview URL, and an iteration loop that doesn't quit.
No installs, no config files, no ceremony. Open a channel and start describing what you want.
Start a conversation in any supported channel — web chat, Slack, Discord, or CLI.
$ cozy init my-project
Write what you need in plain language. Be specific about features, layout, data, and behavior.
"I need a task board with drag-and-drop columns,
user assignment, and a deadline heatmap."
CozyOps generates code and deploys it to a preview URL. Click, test, and verify in your browser.
→ Preview: taskboard.cozy.app/preview
Send follow-up messages to adjust, fix, or add features. Each message triggers a new deploy cycle.
"Add a dark mode toggle and export to CSV."
→ Deploying update 3... done.
Each iteration preserves your previous state. Rollbacks are available for the last 20 deploys. Send cozy rollback to revert.
Every message moves through six stages — from natural language to a live URL. Here's the pipeline in detail.
Your message enters CozyOps through any connected channel. The router identifies project context, detects language/framework intent, and queues the message for processing.
The planner parses your request into a structured task graph: components, routes, data models, API endpoints, and styling directives. Ambiguities are clarified in-channel.
The builder generates production code across your chosen stack. Output is linted, type-checked, and tested against your existing codebase. Conflicts are auto-resolved or flagged.
Built artifacts are pushed to CozyOps' edge infrastructure. Static assets go to CDN, server functions deploy to regions closest to your users. SSL provisioned automatically.
A unique preview URL is returned to your channel. Open it in any browser. CozyOps runs automated smoke tests and reports visual regressions if a previous version exists.
If smoke tests fail or you report an issue, CozyOps enters a repair cycle. It reads error logs, adjusts code, and redeploys — typically in under 30 seconds. The loop continues until the build passes or you intervene.
CozyOps meets you where you already work. Send messages from any supported channel — same engine, same capabilities.
| Channel | Status | Auth | Features |
|---|---|---|---|
| Web Chat | Live | Email / SSO | Full feature set, file uploads, live preview pane |
| CLI | Live | API Key | Scripting, piped input, CI/CD integration, JSON output |
| Slack | Live | OAuth | Thread-based iteration, slash commands, team sharing |
| Discord | Beta | Bot Token | Server channels, DM mode, reaction-based approval |
| VS Code | Beta | Extension Auth | Inline code actions, diff view, integrated terminal |
| GitHub Issues | Soon | GitHub App | Issue-to-deploy, PR generation, label-based triggers |
All channels share the same project state. Start in Slack, continue on the CLI, review in the web dashboard — context follows you.
CozyOps handles infrastructure so you focus on the product. Three deployment targets, zero config required.
Static sites and SPAs deploy to 280+ edge nodes worldwide. Sub-50ms TTFB. Assets fingerprinted, gzipped, and cached at the edge.
API routes and server logic run as isolated functions. Auto-scaled, zero cold-start on popular runtimes. Supports Node, Python, and Go.
Persistent data in SQLite or Postgres — provisioned on demand. Schema managed from your messages. Backups every 6 hours, point-in-time recovery.
Use these patterns in any channel. Natural language works too, but these shorthand forms are faster when you know what you need.
--fn=<name>.
When things don't go as planned, start here. Most issues resolve in one message.
Usually caused by a runtime error in the entry component. Send cozy logs --tail to check for errors. Common fix: send "Fix the blank page error" and CozyOps will auto-diagnose from the logs.
Builds timeout after 120 seconds. If it's stuck, send cozy status to check the queue. Heavy dependencies or large image assets can cause slowdowns. Try: "Optimize build and redeploy."
Be more specific in your follow-up: reference exact sections, colors, spacing, or screen sizes. Example: "Make the header sticky, reduce the hero padding to 2rem on mobile, and change the primary button to green."
Variables set with cozy env set require a redeploy to take effect. Run cozy deploy after setting. For client-side vars, prefix with PUBLIC_ — server-only vars are never exposed to the browser.
Check that your schema was applied: send cozy status and look for the "db" section. If the schema is pending, send "Apply the database schema and seed with sample data." Migrations run automatically on deploy.
Send cozy eject to export the full codebase as a zip or push it to a connected Git repo. The exported project includes a standard build configuration — no CozyOps lock-in. You can always reconnect later.