# CodeMonster.ai > CodeMonster.ai is a desktop AI app platform: your own AI agent (Claude Code, Claude, ChatGPT or any MCP client) builds, deploys and promotes real software on a backend that has carried enterprise workloads for twelve years. One organization license covers every builder and every app. No tokens. No credits. No meter. You bring the AI subscription you already pay for. Apps run on managed cloud infrastructure we operate, built primarily on AWS. The backend is not self-hostable. The AI does not generate platform apps — it assembles governed platform primitives through approximately 100 named, authenticated operations; code generation applies only to custom Vite/React frontends. Custom backend functions are on the roadmap, not shipped. Claims verified 2026-08-14. Comparative vendor claims carry a source and date on the page and a one-quarter shelf life. ## Start here - [/](https://codemonster.ai): Build real software with the AI you already pay for. Desktop AI app platform on a backend that has run enterprise workloads for years; one organization license; nothing metered. - [/download](https://codemonster.ai/download): The desktop app: what it is, what you need (an invite, a license and an MCP-capable AI subscription), and the first ten minutes. Access is invite only during early access. - [/demo](https://codemonster.ai/demo): Request an invite: CodeMonster is invite only. Book a session where we scope what you want to build (or migrate and modernize), strategize the approach, and give training and guidance to ship the first solution. - [/contact](https://codemonster.ai/contact): Talk to us: sales, support, security, press or partners. Desktop-app access starts with an invite request at /demo. ## Product - [/product](https://codemonster.ai/product): How it works: prompt, build, deploy, promote, scale — an AI agent assembling governed platform primitives through named operations. - [/product/platform-primitives](https://codemonster.ai/product/platform-primitives): Objects (real tables), forms, workflows, grids, screens and screenflows: what every platform app is made of. - [/product/environments](https://codemonster.ai/product/environments): Custom frontends promote develop → staging → production, one-way and role-gated, with non-destructive rollback; platform apps publish Current → Testing → Production in one step. - [/product/custom-frontends](https://codemonster.ai/product/custom-frontends): When the renderer is not enough: write a Vite/React frontend and ship it through the same environments, hosting and audit trail. - [/integrations](https://codemonster.ai/integrations): What the platform connects to: email, PDF generation, HTTP calls to Zapier/Make/n8n or any endpoint, push notifications, SSO, Salesforce sync, file storage. ## Bring your own AI (MCP) - [/mcp](https://codemonster.ai/mcp): How bring-your-own-AI works: your Claude, ChatGPT or any MCP client drives the platform over MCP; you keep your model, your keys and your subscription. - [/mcp/operations](https://codemonster.ai/mcp/operations): The control surface: approximately 100 named operations grouped by what they touch; maps in, named writes out; every request authenticated. - [/mcp/claude-code](https://codemonster.ai/mcp/claude-code): Claude Code setup: Claude Code spawns the CodeMonster MCP server over stdio and builds through named platform operations. Live-tested: the config block, the opening calls in order, and what each error means. - [/mcp/claude-desktop](https://codemonster.ai/mcp/claude-desktop): Claude Desktop setup (guide being finalized): Claude Desktop reads MCP servers from its config file and spawns them over stdio. This guide follows the MCP spec and Claude Desktop's documented config; it has not been live-tested yet. - [/mcp/cursor](https://codemonster.ai/mcp/cursor): Cursor setup (guide being finalized): Cursor reads MCP servers from mcp.json and can connect over stdio or HTTP+SSE with a bearer header. This guide follows the MCP spec and Cursor's documented config; it has not been live-tested yet. - [/mcp/chatgpt](https://codemonster.ai/mcp/chatgpt): ChatGPT setup (guide being finalized): ChatGPT reaches MCP servers over the network through its connector settings, so it uses the HTTP+SSE endpoint. This guide follows the MCP spec; it has not been live-tested yet. - [/mcp/other-clients](https://codemonster.ai/mcp/other-clients): Any MCP client setup (guide being finalized): This is the generic HTTP+SSE setup the client guides are built from. The transport and the guardrails are the ones we run; the per-client steps publish as live after we test that client ourselves. ## Pricing and ownership - [/pricing](https://codemonster.ai/pricing): One organization license covers every builder and every app; the TCO calculator prices a realistic year against metered tools using sourced, dated vendor mechanics. - [/pricing/the-meter](https://codemonster.ai/pricing/the-meter): How the category bills — build credits, debug loops, runtime metering, auto-upgrades, per-seat plus credits — with a source and date on every claim. - [/ownership](https://codemonster.ai/ownership): Do I own my apps? Your data is yours (real tables, documented API, export); custom frontends are standard repositories; platform apps run on the platform. ## Security and trust - [/security](https://codemonster.ai/security): For the person who has to say yes: authenticated control surface, the agent acts with your permissions, managed cloud infrastructure we operate (primarily AWS), not self-hostable. - [/security/architecture](https://codemonster.ai/security/architecture): How the pieces fit: platform API, MCP server, custom-frontend deploy chain, hosting. - [/security/data-and-tenancy](https://codemonster.ai/security/data-and-tenancy): Where data lives and how tenants are isolated: row-level tenant filtering, closed storage buckets, HTTPS everywhere. - [/security/governance-and-audit](https://codemonster.ai/security/governance-and-audit): What stops a bad edit and what records it: named operations, staged and previewable transactions, the freeze flag, server-side permissions, append-only logs. - [/security/compliance](https://codemonster.ai/security/compliance): Compliance status, stated plainly: what is in place, what is in progress, and what is not claimed. - [/security/vulnerability-disclosure](https://codemonster.ai/security/vulnerability-disclosure): How to report a vulnerability and what to expect. - [/enterprise](https://codemonster.ai/enterprise): Enterprise: organization license, governance, SSO, environments and audit for larger teams. ## Solutions - [/solutions](https://codemonster.ai/solutions): Who builds on CodeMonster: sales engineers, agencies, operations, developers, and the IT approver. - [/solutions/sales-engineering](https://codemonster.ai/solutions/sales-engineering): Working software built to the prospect's process, in front of them before the next meeting — unmetered, on a backend that stores it. For sales engineers. - [/solutions/agencies](https://codemonster.ai/solutions/agencies): One organization license covers every client app and every builder on your team. Multi-tenant per account, client-facing environments, and an honest handover. - [/solutions/operations](https://codemonster.ai/solutions/operations): Turn the spreadsheet everyone depends on into a governed app — real tables, forms, approvals, and workflows that reach the systems you already run. - [/solutions/developers](https://codemonster.ai/solutions/developers): Approximately 100 named MCP operations, previewable transactions, Vite/React frontends, a Swagger-documented REST API — and the limits, stated plainly. - [/solutions/it](https://codemonster.ai/solutions/it): What builders can and cannot do, the artifacts you can request, and how an organization license moves through procurement — for the person who has to say yes. - [/for-it](https://codemonster.ai/for-it): For IT and security approvers: the short version of the security and governance story. ## Use cases, blueprints and customers - [/use-cases](https://codemonster.ai/use-cases): What people build: field service, inspections, CRM-lite, approvals, intake forms, dashboards, pre-sales solutions. - [/use-cases/presales-solutions](https://codemonster.ai/use-cases/presales-solutions): Customer-specific working software between the discovery call and the next meeting — in the prospect's words, on a real backend, unmetered. - [/use-cases/field-service](https://codemonster.ai/use-cases/field-service): Work orders on a phone: a queue per technician, offline mode, photos and signatures on site, and a PDF report generated when the job closes. - [/use-cases/crm-lite](https://codemonster.ai/use-cases/crm-lite): Companies, contacts, deals and tasks in your vocabulary — assignment workflow, email nudges, one grid per question, and no per-seat bill for the team that builds it. - [/use-cases/inspections-checklists](https://codemonster.ai/use-cases/inspections-checklists): Multi-step form packets, stage-based workflows, corrective actions and a row-level change log — compliance records you can show an auditor without a spreadsheet hunt. - [/use-cases/workflow-approvals](https://codemonster.ai/use-cases/workflow-approvals): A request comes in, approvals route by rule, email goes out at every step, an HTTP call fires when it's done — and there is a record of who said yes, and when. - [/use-cases/intake-forms-surveys](https://codemonster.ai/use-cases/intake-forms-surveys): A public form anyone can submit without an account, tenant-aware, with a change log on every record and a workflow that runs when a submission lands. - [/use-cases/dashboards-custom-frontends](https://codemonster.ai/use-cases/dashboards-custom-frontends): When the renderer isn't the look you need: a Vite/React frontend on the same real tables, shipped develop → staging → production with roles and rollback. - [/templates](https://codemonster.ai/templates): Blueprints: the primitives map and starter prompt for apps that ship on the platform today. - [/customers](https://codemonster.ai/customers): The Closed in 24 Hours series: customer-specific software built between the discovery call and the next meeting. ## Compare - [/compare](https://codemonster.ai/compare): CodeMonster next to the metered AI app builders: what each is good at, how each bills, with sources and dates. - [/compare/hercules](https://codemonster.ai/compare/hercules): CodeMonster vs Hercules: Hercules meters every agent interaction in credits, with auto-billing into the next tier; CodeMonster meters nothing. Strengths conceded, sourced and dated. - [/compare/lovable](https://codemonster.ai/compare/lovable): CodeMonster vs Lovable: Lovable: fast, attractive apps, GitHub sync and a large ecosystem, billed in variable credits plus runtime usage. CodeMonster meters nothing. Sourced. - [/compare/base44](https://codemonster.ai/compare/base44): CodeMonster vs Base44: Base44 (Wix) is the easiest way in, with backend and hosting bundled. It bills two credit pools, one while the live app runs; CodeMonster meters nothing. - [/compare/bolt](https://codemonster.ai/compare/bolt): CodeMonster vs Bolt: Bolt is the fastest loop in the category, with visible tokens and full-stack output. Token cost rises with codebase size; CodeMonster meters nothing. Sourced. - [/compare/v0](https://codemonster.ai/compare/v0): CodeMonster vs v0: v0 by Vercel produces some of the best UI in the category on a platform IT trusts. It bills per user plus credits by model tier; CodeMonster meters nothing. ## Resources - [/docs](https://codemonster.ai/docs): Docs: fastest paths to a first build, setup guides, the control surface, environments, primitives, security. Full reference is moving to codemonster.dev. - [/learn](https://codemonster.ai/learn): Tutorials and walkthroughs. - [/blog](https://codemonster.ai/blog): Blog: teardowns of the meter, engineering notes on environments and the control surface, field notes. - [/blog/maps-not-json-why-the-agent-never-sees-your-schema](https://codemonster.ai/blog/maps-not-json-why-the-agent-never-sees-your-schema): Maps, not JSON: what the agent never sees (Engineering, 2026-08-14): The maps-not-JSON contract: the agent reads compact maps and writes through named operations. Entity-level previews, one carve-out, and why this is governance. - [/blog/what-a-credit-actually-buys-aug-2026](https://codemonster.ai/blog/what-a-credit-actually-buys-aug-2026): What a credit actually buys — August 2026 (The Meter, 2026-08-14): How AI app builders bill: build credits, debug loops, runtime metering, auto-billing, tokens that grow with the codebase, seats plus credits. Sourced and dated. - [/blog/a-demo-is-deployed-software-is-promoted](https://codemonster.ai/blog/a-demo-is-deployed-software-is-promoted): A demo is deployed. Software is promoted. (Engineering, 2026-08-12): Why deployed is not promoted: the develop → staging → production chain, owner/editor/viewer roles, non-destructive rollback and an append-only log. - [/changelog](https://codemonster.ai/changelog): Changelog: dated release notes for the platform, MCP server, desktop app, custom-frontend pipeline, docs and site. - [/roadmap](https://codemonster.ai/roadmap): Roadmap: what shipped, what is next (custom backend functions — coming soon), what is later. No dates promised. - [/faq](https://codemonster.ai/faq): Every question, one page: pricing and the meter, bring your own AI, building, environments, security and IT, ownership, the desktop app. - [/community](https://codemonster.ai/community): Community: where builders meet, office hours, showcase. - [/status](https://codemonster.ai/status): Service status. ## Company - [/about](https://codemonster.ai/about): About CodeMonster.ai by Knomatic: the bet that AI orchestrating a real platform beats generating an app from scratch. - [/partners](https://codemonster.ai/partners): Partners: agencies, integrators, resellers. - [/brand](https://codemonster.ai/brand): Brand: marks, colors, type, what not to do. - [/careers](https://codemonster.ai/careers): Careers. ## Legal - [/legal](https://codemonster.ai/legal): Terms, privacy, DPA, subprocessors, acceptable use. ## Machine endpoints - [/llms.txt](https://codemonster.ai/llms.txt): This file. - [/rss.xml](https://codemonster.ai/rss.xml): RSS feed: blog posts and changelog entries. - [/sitemap-index.xml](https://codemonster.ai/sitemap-index.xml): Sitemap index (drafts and illustrative content excluded). - [/robots.txt](https://codemonster.ai/robots.txt): Crawler rules. ## Contact - Sales: sales@codemonster.ai - Security: security@codemonster.ai (see /security/vulnerability-disclosure) - Press: press@codemonster.ai