Campfire Review
Campfire is an AI native ERP that runs the general ledger, revenue recognition and close for venture backed software companies, replacing QuickBooks or NetSuite with a system where an in house accounting model drafts the entries and the finance team approves them.
Independently scored, one dimension at a time. Every dimension is sourced, and we say whether a claim is published, reported, or estimated.
There is a genuine first party MCP server at api.meetcampfire.com/mcp with 12 tools, plus a Claude Desktop connector listing, and the tools cover chart of accounts, transactions, entities, vendors, departments, tags, income statement, balance sheet, cash flow, budgets, contracts and aging. Every one of those 12 is a read; the MCP store post of 14 May 2026 argues on principle against giving an external AI write access to the ledger, so writes stay in the REST API under an admin or clerk token. In product, Ember agents and the LAM accounting model do the writing with a human approval threshold, which is a strong story for staff and a weaker one for an outside agent.
Migration Agent, announced 3 September 2026, moves the general ledger at transaction level in about 15 minutes and produces a reconciliation workbook of live formulas so the finance team can tie the old balance sheet to the new one itself, and Campfire will build a sandbox on the buyer own data before signature. Every write in the migration requires human approval, and prepaid and fixed asset schedules are rebuilt by the implementation team rather than copied. The published go live window is inconsistent: under a month on the CFO Buyout comparison table, four to eight weeks on the implementation page, and around 8 to 12 weeks in the core accounting FAQ, all three live on 6 September 2026.
The developer docs list 459 pages across 13 API groups, with 87 revenue recognition endpoints, 78 core accounting endpoints and full create paths for journal entries, intercompany journal entries with per entity exchange rates, bills, invoices and fixed assets. Webhooks are first class: HMAC SHA256 signing, eight object families from Invoice through Contract, and a field level changes diff on every delivery. Weak points are that no rate limit is documented anywhere in the docs, the API and MCP still run on api.meetcampfire.com while the marketing site has moved to campfire.ai, and the site publishes 66 integration pages against a home page claim of 100 plus native integrations.
The core is real: multi entity consolidation with automatic intercompany eliminations, 180 plus currencies and unlimited entities on the home page, native ASC 606 with contract level audit trails, and an ASC 842 lease module in the changelog. Multi book accounting went live on 27 May 2026 but is one primary entity plus one adjusting entity, covers only trial balance, balance sheet and income statement, and a period cannot be locked until both books are complete. Campfire states SOC 1 and SOC 2 at Type 1 and Type 2 and 1,200 plus granular permissions, but its own compliance FAQ affirms ASC 606 without ever affirming IFRS 15.
The home page promises dedicated in house support from accountants who have closed books, the CFO Buyout page names a dedicated Slack channel and phone support, and the implementation page names five CPAs and a CFA on the implementation team. Against that, no response time target, support tier or uptime commitment is published anywhere, status.campfire.ai renders no incident history without scripting, and the customers page 4.8 out of 5 CSAT figure is self reported with no sample size. G2, Capterra and Trustpilot all returned 403 to a scripted fetch on 6 September 2026, so there is no readable third party support evidence.
Financial statements are native and API callable, the report builder is drag and drop with drill down to the transaction, and the close checklist is built in, which the core accounting FAQ positions as replacing FloQast. The Flux Analysis Agent writes variance commentary against any account, department or cost center and exports for board decks, and the 17 August 2026 changelog added balance sheet roll up by account subtype. The limits are the young ones: multi book side by side reaches only trial balance, balance sheet and income statement, and no consolidated statutory or local GAAP reporting pack is documented.
Campfire markets unlimited entities and 180 plus currencies, and the revenue page says usage data of billions of rows can sit in Snowflake or a warehouse. The named references are large but few: PostHog at a 1.4 billion dollar valuation, Replit past 200 million dollars of ARR, and a partnership with NYSE listed LimaOne claimed in the Series B post. Crunchbase News reported on 15 October 2025 that the company had grown from 10 to 40 employees, so the failure modes at high entity and transaction counts have no public track record yet.
There is no pricing page: campfire.ai/pricing returned 404 on 6 September 2026, the sitemap contains no pricing URL, and no list price, seat price or entity price appears on any product page. The savings calculator publishes dollar figures for the legacy stack it is displacing, 100,000 dollars of implementation fees and three 50,000 dollar line items, and none of them are Campfire fees. The only published Campfire dollar amount is the 5 million dollar CFO Buyout Fund, which pays out an incumbent contract rather than describing what Campfire charges.
The migration proof is real. The commercial terms are entirely private.
Written by the Audit Friendly research team. No vendor edits, no sponsored placement.
What a controller is really buying is a general ledger built after 2020 around an accounting model of its own. Multi entity consolidation, 180 plus currencies, native ASC 606 and an ASC 842 lease module sit in the core rather than in a priced add on, the close checklist is built in, and Ember agents draft accruals, transaction matches and flux commentary for a person to approve under a confidence threshold. Migration Agent, announced on 3 September 2026, moves the ledger at transaction level in about 15 minutes and hands back a reconciliation workbook of live formulas, which is the most concrete answer any ERP vendor currently gives to the question of how a finance team proves a migration worked.
The catch is that almost nothing commercial is published. There is no pricing page: campfire.ai/pricing returned 404 on 6 September 2026. The Terms of Use state that they apply to the website and expressly do not apply to the services, which are governed by a separate agreement nobody outside a deal can read, and no uptime commitment, support response target or API rate limit appears anywhere. Depth tracks the age of the company. Multi book accounting is one primary entity plus one adjusting entity across three statements, the first party MCP exposes 12 tools and every one is a read, and the site publishes 66 integration pages against a home page claim of 100 plus native integrations.
Confirm four things in writing before signing. The quote broken out by module, entity and user, with the renewal uplift capped in the first contract. The services agreement, the data processing agreement and the uptime commitment, since none of the three are public. A named go live date, because the site publishes under a month, four to eight weeks and 8 to 12 weeks at the same time. And a list of the specific integrations that will be live on day one, after a February 2026 thread on r/Accounting in which a customer said a promised billing tool integration and an Avalara integration did not exist at implementation.
- A venture backed software company outgrowing QuickBooks that needs multi entity consolidation, multi currency and ASC 606 in one ledger instead of three tools.
- A lean accounting team that wants agents drafting accruals, matches and flux commentary under an approval threshold, with every action attributed in the audit trail.
- A controller who will not take a migration on trust and wants a reconciliation workbook tying the old balance sheet to the new one account by account.
- A buyer who needs a published price, a public services agreement or a contractual uptime commitment before the first sales call, because none of the three exist.
- A group running parallel statutory books beyond a single adjusting entity, or needing local GAAP reporting packs and country by country statutory filings out of the box.
- A team that wants an external AI agent to post to the ledger, since the first party MCP exposes 12 read tools and no writes at all.
The jobs a controller actually hires Campfire for
Jobs, mapped to how finance teams actually buy.
Watch the same task in each tool
Forget the 40-row feature grid. Pick a finance workflow and see how this tool and its closest peers actually do it, with our verdict on who wins for whom.
Compare on what matters
What it actually costs
Here's what it really costs: published rates where a vendor lists them, aggregated quote data where they don't, plus a path to your own number.
campfire.ai/pricing returned 404 on 6 September 2026 and the sitemap contains no pricing URL. No seat price, entity price or module price appears on any product page, so every figure comes out of a sales conversation.
Campfire states that ASC 606 revenue recognition is in the core platform rather than a priced module, and that the built in close checklist replaces standalone close tools such as FloQast. Lease accounting under ASC 842 shipped as a native module in June 2026.
The only dollar figure Campfire publishes about its own commercials. The CFO Buyout page offers a 5 million dollar fund to buy a prospect out of an existing ERP contract. It is an inducement to switch, not a statement of what Campfire charges.
What it actually takes to go live
All three were live on 6 September 2026. The CFO Buyout comparison table says implement in less than a month. The implementation page says most teams are live in four to eight weeks, with multi entity migrations off larger systems at six to eight weeks. The core accounting FAQ says around 8 to 12 weeks. In September 2026 accountants were publicly complaining about Campfire and Rillet advertising two week conversions. Get a single named go live date into the order form rather than accepting whichever number the deck shows.
The first party MCP server documented at docs.campfire.ai/guides/ai-integration exposes 12 tools, and every one is a retrieval or a generated report. The MCP store post of 14 May 2026 makes the position explicit, arguing against routing an external AI with write access to the ledger. Writes go through the REST API with an API user scoped as admin, clerk or view only, where a clerk can post draft entries only. Plan any agent workflow around a token, not around the connector.
campfire.ai/pricing returned 404 on 6 September 2026. The Terms of Use published at campfire.ai/terms-and-conditions state in their second paragraph that they apply to the website and expressly do not apply to use of Campfire services, and that a separate services agreement documents those. Term length, renewal mechanics, the data processing agreement, uptime commitments and API rate limits are therefore all invisible until a deal is underway. Ask for all of them in writing before the first quote is discussed.
The home page claims 100 plus natively built integrations while the site publishes 66 integration pages, counted from campfire.ai/integrations and the sitemap on 6 September 2026. In a February 2026 thread on r/Accounting a customer said a promised billing tool integration and an Avalara integration did not exist when they reached implementation, and a Campfire account created that same month replied in the thread. Name every integration you are counting on, with its go live date, in the order form.
The multi book announcement of 27 May 2026 describes one primary entity plus one adjusting entity, with adjusting journal entries posted only to the secondary book. Multi book reporting reaches the trial balance, the balance sheet and the income statement, with more reports described as coming. A period cannot be locked until both books are complete. Groups running statutory local GAAP alongside IFRS and management books in several jurisdictions should test that shape against their own structure before signing.
Scored on what an outside agent can actually reach: the documented API, how it authenticates, and whether the vendor ships an MCP server.
Campfire runs a first party MCP server and is listed as a Claude Desktop connector, which puts it ahead of most of the ERP category on paper. The surface is narrow and deliberate: 12 tools covering chart of accounts, transactions, entities, vendors, departments, tags, income statement, balance sheet, cash flow, budgets, contracts and aging, and every one of them is a read or a generated report.
The company argues the position rather than hiding it. Its MCP store post of 14 May 2026 says routing AI requests through an external tool with write access to the ledger puts financial data outside the customer's control and outside the audit trail, and that Campfire does not work that way. Writing is done inside the product by Ember agents, backed by a proprietary model the company calls LAM, under a confidence threshold the customer sets, with every action logged and attributed.
For an outside agent that needs to post, the path is the REST API rather than the MCP: an API user scoped as admin, clerk or view only, authenticated with an Authorization Token header, where a clerk can post draft entries only. All of these figures are vendor documented and were read on 6 September 2026.
Close the month
Who wins for whom: A close enforced by a proven checklist at scale: NetSuite. The close, consolidation and FX built into the ledger: Rillet. Variance commentary written for you, if you can do without a documented statutory reporting pack: Campfire.
Campfire
A checklist plus a flux agent. A built-in close checklist, reporting that drills to the transaction, and a flux analysis agent that writes variance commentary.
Where it loses: No consolidated statutory or local GAAP reporting pack is documented, and it publishes three different go-live timelines at once.
- Reporting & close: 65/100
- Time to live: 4 to 12 weeks
Source: AF score rationales: Reporting & close 65, Implementation 71; Campfire watch-outs.
Watch: From 20-Day Close to 6: How Boulder Care Runs Finance with Campfire 2:27 · Customer story · Campfire AI on YouTube (official)
NetSuite
A checklist that enforces the close. The Period Close Checklist sequences and enforces close tasks, and saved searches cover most controller reporting without leaving the system.
Where it loses: Reviewers report slowness at month end as custom scripts and searches pile up, and implementation runs from three months to well past a year.
- Reporting & close: 80/100
- Time to live: About 100 days
Source: AF score rationales: Reporting & close 80, Implementation 50.
Watch: Simplify Month-End Close in NetSuite 1:51 · Consultant walkthrough · Third-party consultant walkthrough
Rillet
Close built into the ledger. A configurable close checklist with owners and deadlines, period locking by entity and AI drafted flux analysis, with consolidation and FX in the platform.
Where it loses: The automation rates quoted on its own site do not agree with each other, and customers flag billing as the weakest area.
- Reporting & close: 76/100
- Time to live: 4 to 8 weeks
Source: AF score rationale: Reporting & close 76; Rillet watch-outs.
Watch: Rillet product demo: the AI native ERP 2:57 · Official demo · RilletHQ on YouTube (official)
Reconcile the bank
Who wins for whom: Machine matching that leaves only exceptions: Rillet. Reconciliation as the month runs: Campfire. Matching rules you can extend, with daily automated imports: NetSuite.
Campfire
Reconciles through the month. Bank and card accounts reconcile as the month runs rather than at month end, with AI categorisation that learns from your data and approvals by dollar threshold.
Where it loses: The 90 percent time-saved figure has no published method, and the documentation does not spell out how banks connect.
- API & automation: 70/100
- Time to live: 4 to 12 weeks
Source: Campfire product demo (2026) and llms.campfire.ai; AF score rationale: API & automation 70.
Watch: Campfire product demo (2026), transactions and bank reconciliation 9:16 · Vendor product demo · Campfire AI (official)
NetSuite
Rule-driven matching at scale. Match Bank Data applies three default matching rules plus any you write, and automated imports can run daily through a bank connectivity SuiteApp.
Where it loses: Each import tops out at 10,000 transactions and 500 accounts, and bank connectivity is a SuiteApp or partner setup rather than on by default.
- API & automation: 78/100
- Time to live: About 100 days
Source: Oracle NetSuite help on bank data import and reconciliation rules; AF score rationale: API & automation 78.
Watch: NetSuite bank matching and reconciliation: system rules 6:21 · Consultant walkthrough · Fusion CPA on YouTube
Rillet
Machine matching, exceptions only. Plaid feeds from 12,000 plus institutions, with matching that handles one-to-many, partial set-offs, bank fees and FX variance so the team works only exceptions.
Where it loses: The 95 percent auto-match rate is Rillet's own figure and undefined, like its other automation numbers.
- API & automation: 79/100
- Time to live: 4 to 8 weeks
Source: Rillet bank reconciliation product page, September 2026; AF score rationale: Reporting & close 76.
No public demo of this task. Ask for a sandbox run into your own system before you sign.
Campfire, kept current
Campfire FAQ
There is no published price. campfire.ai/pricing returned 404 on 6 September 2026, the sitemap carries no pricing URL, and no seat, entity or module price appears on any product page, so every figure comes from a quote. The savings calculator does publish dollar amounts, 100,000 dollars of implementation fees plus three 50,000 dollar line items for close checklist software, revenue automation software and ERP consultants, but those are Campfire assumptions about the legacy stack it is replacing rather than its own fees. The only published Campfire figure is the 5 million dollar CFO Buyout Fund, which pays out an incumbent ERP contract. Ask for the quote broken out by module, entity and user, and get the renewal uplift capped in the first contract.
Nothing about them is public. The Terms of Use at campfire.ai/terms-and-conditions state that they apply to the website and expressly do not apply to use of Campfire services, and that a separate services agreement documents those terms, so the term length, the renewal mechanics, the data processing agreement and any service level commitment all sit in a private document. On the way in, Migration Agent moves the general ledger at transaction level and subledger records such as invoices and bills carry a reference back to the journal entry, so prior periods stay queryable. Nothing published describes the export on the way out. Ask for the services agreement, the data processing agreement, the uptime commitment and a written data export format before signing.
The site publishes three different answers at once, all live on 6 September 2026. The CFO Buyout comparison table claims implementation in less than a month. The implementation page says most teams are live in four to eight weeks, with multi entity migrations off larger systems at six to eight weeks. The core accounting FAQ says implementations take around 8 to 12 weeks. The data move itself is genuinely fast: Migration Agent loads years of journal entries in about 15 minutes with a person approving every write, and prepaid and fixed asset schedules are rebuilt by the implementation team rather than copied across. Campfire will also build a sandbox on the buyer own data before signature, which is the cheapest way to test the claim.
It can read, and it cannot post. Campfire runs a first party MCP server documented at docs.campfire.ai/guides/ai-integration with 12 tools covering chart of accounts, transactions, entities, vendors, departments, tags, income statement, balance sheet, cash flow, budgets, contracts and aging, and it is listed as a Claude Desktop connector. Every one of those tools is a retrieval or a report, and the MCP store post of 14 May 2026 argues explicitly against routing an external AI with write access to the ledger. Writes go through the REST API using an API user whose role is admin, clerk or view only, and a clerk can only post draft entries. Webhooks are HMAC SHA256 signed across eight object families, and no rate limit is documented anywhere in the API docs.
Campfire alternatives
Ask us anything
Answered only from our own published research on this tool, never from general internet noise. If we cannot answer it well, our research agents will dig in and publish a sourced answer.