Formcms is live · free · last verified 6 Nov 2026 · viability at risk
Formcms
Open-source agentic headless CMS on ASP.NET Core that generates REST and GraphQL APIs from your data model.
FormCMS v1.0 makes sense if you're a .NET shop that wants generated CRUD and GraphQL APIs plus CRUD hooks as escape hatches, and you don't mind running the Docker Compose stack yourself. The agentic drafting sits in the core rather than bolted on, which is unusual at this stage. If zero infrastructure is your priority, managed CMS options will ask less of you.
Verdict generatedVerified 8d ago · liveness 39/100 · cite: rightaichoice.com/tools/formcms
- .NET teams that want a self-hosted headless CMS with generated CRUD and GraphQL APIs
- React developers using FormCMS as a backend with AI-assisted page generation
- Content teams that want AI drafting, optimization and organization over manual editing
- Developers who want CRUD hooks to extend backend behavior without forking the framework
- Teams that need a fully managed cloud CMS and don't want to run infrastructure
- Non-technical users who need a no-code site builder with zero Docker or deployment setup
- Teams with no .NET or container experience and nobody to own the deployment
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip FormCMS if nobody on your team wants to own a Docker Compose stack, database provider choice and container configuration recovery.
You pay the infrastructure bill, not a license fee — the app container and a Postgres, SqlServer or MySQL instance are yours to run and monitor.
FormCMS is open source and self-hosted, so your spend goes to infrastructure and engineering time rather than per-seat CMS licensing — a different cost shape from managed headless CMS platforms that bill by seats and editions. For a .NET team already running containers, the marginal cost of adding FormCMS is a database and a container. For a team without container experience, the cheaper license is offset by the labor of owning deployment, backups and recovery.
In short
Formcms — Open-source agentic headless CMS on ASP.NET Core that generates REST and GraphQL APIs from your data model. Best for .NET teams that want a self-hosted headless CMS with generated CRUD and GraphQL APIs, React developers using FormCMS as a backend with AI-assisted page generation, Content teams that want AI drafting, optimization and organization over manual editing. Free to use.
What is Formcms?
Formcms — Open-source agentic headless CMS on ASP.NET Core that generates REST and GraphQL APIs from your data model. Best for .NET teams that want a self-hosted headless CMS with generated CRUD and GraphQL APIs, React developers using FormCMS as a backend with AI-assisted page generation, Content teams that want AI drafting, optimization and organization over manual editing. Free to use.
FormCMS is an open-source headless CMS built on ASP.NET Core with a React frontend, now at v1.0 with what the vendor calls an agentic content core. The workflow is data-driven: define your content structure first, and FormCMS generates REST CRUD endpoints and a GraphQL API from that model. CRUD hooks let .NET developers extend backend behavior without forking the framework. Non-developers aren't locked out. An AI page generator and a visual page designer let content teams build pages without templates, and a Node.js AI Schema Builder (formmate) makes schema creation easier. Recent vendor guides cover running FormCMS as the backend for Vite + React frontends built with AI coding assistants like Antigravity and Cursor. Deployment is a single Docker Compose stack behind Nginx on port 5000: /api/* proxies to the ASP.NET Core CMS on 5001, while /mate, /admin, /portal and /static go to the Node.js service on 3001. You pick SQLite, Postgres, SqlServer or MySQL via DATABASE_PROVIDER. If the database is unreachable the app drops into a Setup Mode at /mate/settings instead of crashing. Stash, a PWA companion app, adds a mobile-app-style experience on the same backend. For teams already on the Microsoft stack who want AI automation inside a CMS they host themselves, FormCMS is a plausible fit, provided you're ready to own the stack. Compare it to Strapi or Contentful only if you've accepted that self-hosting trade-off.
Key features
- Agentic AI core that drafts, optimizes and organizes content autonomously
- Auto-generated REST CRUD APIs from your content model
- Generated GraphQL API for flexible content queries
- AI page generation for non-developers, no templates required
- Visual page designer for layouts without hand-coding
- CRUD hooks for backend extensibility in .NET
- AI Schema Builder (formmate) on the Node.js layer
- Data-driven modeling: define the data structure, build UI upward
- Docker Compose deployment with Nginx gateway on port 5000
- Nginx routing: /api/* to ASP.NET Core, /mate /admin /portal /static to Node.js
- Selectable database provider via DATABASE_PROVIDER: SQLite, Postgres, SqlServer, MySQL
- Setup Mode at /mate/settings when the database is unreachable
- Runtime-updatable configuration via formcms.settings.json
- Stash PWA companion app for a native-style mobile experience
- Integration guides for Vite, React and AI coding assistants (Antigravity, Cursor)
Behind the verdict
We'd reach for FormCMS when the team already speaks ASP.NET Core and wants the content model to be the source of truth. Define the structure, get REST and GraphQL endpoints, then use CRUD hooks to add behavior without forking. That's a shorter path than standing up a separate GraphQL engine next to a generic CMS. The agentic angle is the differentiator the vendor pushes. AI drafts, optimizes and organizes content, and non-developers can build pages with the AI page generator and visual designer. In practice, that means a content team can ship without waiting on a developer for every layout change. Where it bites: you own the stack. The Docker Compose deployment is a real one, with Nginx routing /api/* to the ASP.NET Core service and /mate, /admin, /portal and /static to the Node.js service. Persist formcms.settings.json to a volume or docker-compose down takes your configuration with it. Upgrades, backups and uptime are yours. The Setup Mode fallback at /mate/settings is a thoughtful touch. If the database is unreachable, the app doesn't crash; you unlock the Database tab and fix the connection string. Pick the provider with DATABASE_PROVIDER: SQLite, Postgres, SqlServer or MySQL. The vendor's scalability claims lean on SQLite for simple cases, so heavier workloads should probably start on Postgres. Closest alternative depends on your stack. Strapi is the obvious comparison for a Node-based headless CMS; Contentful or Strapi Cloud if you want managed hosting. For a Vite + React team using an AI assistant like Cursor, FormCMS as a generated backend is a reasonable shortcut, though you're trusting a v1.0 product to hold up in production. The Stash PWA companion is a nice extra for mobile-shaped content, not a reason to choose the tool by itself. Treat FormCMS as a
Limitations
- FormCMS is self-hosted, so you own upgrades, backups and uptime.
- The deployment guide warns that formcms.settings.json lives inside the container and is lost on docker-compose down or container recreation unless you map a volume to /config — set CONNECTION_STRING correctly on the first run or plan for that recovery step.
- Database selection is a runtime setting (0=SQLite, 1=Postgres, 2=SqlServer, 3=MySQL) and changing it later means editing the file in the container or using the System Settings UI at /mate/settings.
- The documented architecture consolidates Nginx, the Node.js frontend/backend and the ASP.NET Core CMS into a single app container, which simplifies setup but concentrates failure domains: a restarting .NET backend shows as a 502 until it comes back, and Nginx serves a 503 'system is restarting' page during startup.
- The available evidence does not name the specific AI model powering the agentic features.
as of 2026-10-13
Researching Formcms? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Formcms still active?
Formcms is live · free · last verified 6 Nov 2026 · viability at risk.
Viability score
How well maintained and how widely used is Formcms? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: November 2026
How we score →What do users say about Formcms?
What people actually say about Formcms — is it worth it?
We scanned public community sources for Formcms on Nov 8, 2026 and could not establish that the discussion we found is about this tool rather than something else sharing its name. Only 1 of the posts we fetched could be positively tied to Formcms. Rather than publish a sentiment score built on the wrong subject, we publish nothing here and re-run the scan.
How we verified this
Every listed fact about Formcms — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 6 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified Formcms 13 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed our verdict, description, summary, who should skip it, features, who it suits
- — changed our verdict, who it suits, description, features, hidden costs, limitations, switching in, switching out, who should skip it, pricing fit, setup time, summary, use cases
- — changed SSL certificate
- — changed who should skip it, description, our verdict, summary, who it suits, features
- — changed link health
- — changed use cases, switching in, setup time, switching out, pricing fit, summary, who it suits, who should skip it, features, our verdict, hidden costs, description, limitations
Showing the 6 most recent of 13 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Formcms cost in 2026?
Formcms: Free to use. Pricing last verified 6 Nov 2026.
Where the pricing makes sense
The company stage and team size where Formcms's pricing actually pencils out — and where peers do it cheaper.
FormCMS is open source and self-hosted, so your spend goes to infrastructure and engineering time rather than per-seat CMS licensing — a different cost shape from managed headless CMS platforms that bill by seats and editions. For a .NET team already running containers, the marginal cost of adding FormCMS is a database and a container. For a team without container experience, the cheaper license is offset by the labor of owning deployment, backups and recovery.
Has Formcms' pricing changed?
No plan price for Formcms has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Formcms?
Pick Formcms if you are .NET teams that want a self-hosted headless CMS with generated CRUD and GraphQL APIs, React developers using FormCMS as a backend with AI-assisted page generation, Content teams that want AI drafting, optimization and organization over manual editing, Developers who want CRUD hooks to extend backend behavior without forking the framework.
Look elsewhere if you are Teams that need a fully managed cloud CMS and don't want to run infrastructure, Non-technical users who need a no-code site builder with zero Docker or deployment setup, Teams with no .NET or container experience and nobody to own the deployment, Buyers who want a vendor-managed upgrade path, backups and support SLAs.
Skip it if Skip FormCMS if nobody on your team wants to own a Docker Compose stack, database provider choice and container configuration recovery.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Formcms actually fits — and what changes day-one when you adopt it.
You model your content types, let FormCMS generate REST CRUD endpoints and a GraphQL API, then add custom business logic through CRUD hooks instead of forking the framework.
Outcome: A working API surface for your content without hand-writing controllers, with extension points where your business rules actually live.
You run the FormCMS Docker Compose stack, build your frontend in Vite and React with an AI assistant like Antigravity or Cursor, and point it at the generated /api endpoints.
Outcome: A shipped frontend backed by a real CMS and GraphQL API, with no .NET code written by you.
You use the AI page generator and visual page designer to assemble pages, while the agentic core drafts, optimizes and organizes the content behind them.
Outcome: Pages built without templates or hand-coding, published from the same backend your developers query.
Use cases
- Build a blog or documentation site with AI-assisted content drafting
- Create a headless backend for a React or mobile app using generated REST/GraphQL APIs
- Generate a content schema through the AI Schema Builder instead of writing models by hand
- Design landing pages with the visual page designer and AI-generated components
- Extend CRUD operations with hooks for custom business logic in .NET
- Run a content hub for multi-channel distribution across web, PWA and mobile
- Stand up a Postgres- or SQLite-backed CMS from a single Docker Compose container
Setup time & first value
How long it actually takes to get something useful out of Formcms — broken out by persona, not the marketing-page minute.
For a .NET developer: build the image, run the container, set DATABASE_PROVIDER and CONNECTION_STRING correctly on first run — roughly an afternoon to a working API. For a React developer: the same deployment plus a Vite project pointed at /api, so add a day for the frontend wiring. For a non-developer: no deployment path exists that avoids Docker, so first value depends on someone else standing
Switching to or from Formcms
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From a hand-rolled ASP.NET Core API: define the same content model in FormCMS and let it generate the CRUD and GraphQL endpoints you were writing manually.
- →From another headless CMS: recreate your content structure in the AI Schema Builder, then export and import your entries against the generated APIs.
- →From SQLite to Postgres or SqlServer: change DATABASE_PROVIDER in formcms.settings.json or via the System Settings UI at /mate/settings and restart.
- ↗To a managed headless CMS: export your content through the generated REST or GraphQL API, since the data model is the source of truth rather than templates.
- ↗To a separate GraphQL engine: your schema is already modeled in FormCMS, so the content types map across without re-deriving structure from the UI.
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Formcms”, and we withheld 6: 6 could not be judged, because “Formcms” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Formcms.
Official links
What are the best Formcms alternatives?
The closest alternatives to Formcms we list are Kerlig, Clico and WordAi. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Kerlig | Paid | Pricing not published | — |
| Clico | Freemium | Pricing not published | — |
| WordAi | Paid | Pricing not published | — |
Alternatives to Formcms
View all
Tools that pair well with Formcms
Common stack mates teams adopt alongside Formcms, with the specific reason each pairing earns its keep.
Kerlig
Kerlig puts 350+ AI models one ⌥+space hotkey away in any Mac app for proofreading, rewriting and chat.
Clico
Clico is a screen-aware AI creative studio that turns a photo or open page into images, video, music, websites and browser games.
WordAi
WordAi's AI text rewriter restructures whole sentences to produce unique, human-reading rewrites of content you already have.
Formcms vs its closest rival
Formcms's closest head-to-head is with Spider Cloud.
Our Formcms vs Spider Cloud verdict written Jul 3, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
Frequently asked questions
Categories
Best-of guides
For makers of Formcms
- Get a Verified Listing for Formcms ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used Formcms? Help shape our editorial sentiment research.