Campfire vs Rillet (2026)

Connectors from Campfire's MCP store give Ember live access to Ramp, Stripe, HubSpot, Salesforce and other tools after a standard OAuth sign in, so it can draft accruals from approved purchase orders in procurement, reconcile Stripe payments or turn contracts into invoices. In every example the outside tool is read and the action lands in Campfire's own books. Bank feeds, billing and expense tools bring data in the same direction.

Sourcecampfire.ai/blog/campfire-is-the-first-erp-with-an-mcp-storeread 2026-10-13

The systems the agents act across are named. Native Integrations is a product line, presented as the single source of financial data. Rillet is an agent of Plaid Financial Ltd for regulated bank account information. Salesforce, Stripe, Ramp, Brex, Rippling and Snowflake make up the connected stack, with continuous bank and processor syncing and native Stripe payout matching, workflow agents handle the data pulls, and the MCP surface reaches Salesforce and Snowflake.

SourceRillet, rillet.com/product/aura-ai, rillet.com/product/native-integrations named in navigation, and info.rillet.comread 2026-09-07

Ember Agents split into continuous agents that work through AP, AR, matching, policy monitoring and accruals on their own, and on demand agents that sit on the monthly close checklist and run flux analysis, close prep and board reporting the same way every period. Ember Skills carry multistep procedures. One search for unrecorded liabilities gathers six sources, runs five detection tests, validates and classifies each candidate and drafts entries, and one team's skill coordinates six sub skills to build a department P&L.

Sourcecampfire.ai/blog/introducing-ember-agentsread 2026-10-13

Customers compose multi step workflows that agents run. Workflow agents complete sophisticated accounting tasks end to end, reliably and repeatably, with the customer writing the rules in plain English and Aura handling the schedule, the data pulls and the handoffs. Approval workflows route journal entries, sync events and agent proposals with materiality tiers, and close management runs task checklists across the period. Because the rules are written in plain English, customers compose the flow themselves instead of running a fixed pipeline.

SourceRillet, rillet.com/product/aura-ai and rillet.com/product/security-and-permissionsread 2026-09-07

Continuous agents run around the clock as transactions arrive from bank feeds, billing and expense tools, without anyone starting them. On demand agents fire on the close calendar once they are on the checklist. People can also start work by mentioning @AskEmber in a Slack channel, and findings go out to Slack or email so a team need not log in.

Sourcecampfire.ai/blog/introducing-ember-agentsread 2026-10-13

Three kinds of trigger start the agents. Aura runs continuously, always on, watching for anomalies, flagging exceptions and proposing accruals as they happen. Workflow agents run on schedules Aura handles. Events drive the rest, since continuous close is a real time architecture in which every transaction is fully processed the moment it arrives, with continuous bank and processor syncing, so transaction arrival drives the agent chain instead of a batch cycle.

SourceRillet, rillet.com/product/aura-ai and info.rillet.comread 2026-09-07

Agents work from the live general ledger, with every action sourced to the GL data underneath it. Accounting Intelligence, Campfire's own model trained on millions of accounting transactions, learns each customer's chart of accounts, vendors, policies and patterns from its own history to code, match and suggest accruals. Connected tools add procurement, billing and CRM data at the moment Ember needs it.

Sourcecampfire.ai/accounting-intelligenceread 2026-10-13

Aura answers from the customer's live general ledger and company configuration, which feed an intelligence layer. It answers natural language questions about vendors, accounts, balances or any cut of the data with numbers sourced from the GL, working against real ledger data, not a stale copy. The ledger is a persistent, structured, continuously updated store of the customer's financial record that outlives any run and stays queryable.

SourceRillet, rillet.com/product/aura-airead 2026-09-07

Between runs, Ember carries forward only the procedures a team sets down and the books themselves. Ember Skills are procedures a person defines once, with a name, a description and instructions, that Ember follows each time, and Accounting Intelligence picks up coding patterns from the customer's transaction history. Neither is a store the agents keep for themselves, and nothing shows Ember keeping a conversation history or remembered context.

Sourcecampfire.ai/blog/standardize-close-process-ember-skillsread 2026-10-13

Rillet says Aura remembers how the team works, so it answers, acts and reconciles the way the team would. That describes adaptation, not a memory feature. There is no named memory construct, stated scope or lifetime, recall surface for each user or workflow, or deletion path. The live general ledger and company configuration feeding the intelligence layer are the application's data and the customer's setup, not memory, and learned working patterns absorbed into behavior are not a memory a customer can inspect.

SourceRillet, rillet.com/product/aura-airead 2026-09-07

The team sees each agent's output, reviews what needs review and approves before anything posts. Confidence thresholds draw the line between results that apply automatically and results that wait, and the team moves that line as its trust grows, or keeps every item manual. Skills stop at drafted journal entries, and invoices drafted from contracts in connected tools wait for approval.

Sourcecampfire.ai/blog/introducing-ember-agentsread 2026-10-13

Oversight is built into the product. Nothing posts automatically without approval, and every agent action is proposed to a human and posts only once approved. Approval workflows are tiered to materiality with configurable dollar thresholds, such as fifty thousand dollars to the Controller and five hundred thousand to the CFO.

AI agent proposals are routed through the same workflows as journal entries and sync events, and under segregation of duties agents prepare and humans authorize, with role-based access. Every step can be approved and edited. The customer configures that gate, and it sits on the action that matters, posting to the general ledger.

SourceRillet, rillet.com/product/security-and-permissions and rillet.com/product/aura-airead 2026-09-07

Access is set by workspace permissions grouped by module, from accounting, revenue and reports to cash, close, organization and Ember AI, with an access tier per resource. Only admins create OAuth apps, whose scopes cap what a connected tool can ever request, and a person authorizing one can grant no more than their own rights. AskEmber answers only Slack users linked to a Campfire account, within their permissions. Campfire holds SOC 2 Type 2 and SOC 1 Type 2 reports.

Sourcedocs.campfire.ai/guides/oauth-apps.mdread 2026-10-13

Rillet holds SOC 1 and SOC 2 Type II, with annual third-party audits and reports available for review. It encrypts data with AES-256 at rest and TLS 1.2+ in transit, runs continuous monitoring with penetration tests and commits to GDPR.

Controls include enterprise SSO via Google, Microsoft Entra and Rippling, three-tier role-based access (Owner, Admin, Accountant plus view-only) with no seat limits and immediate permission changes under full audit history, segregation of duties enforced for AI agents as for people, period locking and subledger locks for each entity. Audit logging is part of the same controls.

SourceRillet, rillet.com/product/security-and-permissionsread 2026-09-07

Every agent action is logged and sourced to the general ledger data behind it, and every journal entry, reconciliation or drafted invoice Ember creates sits in the audit trail attributed to Ember, like any other user. Each categorization shows why it was made. On demand agent runs are attributed and ready to export, and AskEmber replies carry the same reasoning and supporting detail as in Campfire.

Sourcecampfire.ai/blog/introducing-ember-agentsread 2026-10-13

One hundred percent of AI actions are logged, with every query, proposal, approval and rejection recorded with timestamp and reasoning, every read access logged with full attribution, every permission change under full audit history, and every period lock and unlock logged with reason and timestamp. Together these reconstruct what an agent did, why, and who authorized it, alongside an audit trail by default and the accrual agents' plain-language rationale.

SourceRillet, rillet.com/product/security-and-permissions and rillet.com/product/aura-airead 2026-09-07

Every Campfire production system, from the application servers and databases to file storage, caching and search, runs on Amazon Web Services in the us-west-2 region, for every customer. Data is encrypted in transit and at rest, recovery data sits apart, and disaster recovery is tested. There is no choice of region, private cloud or self hosted edition.

Sourcetrust.campfire.ai/?tab=subprocessorsread 2026-10-13

The platform is hosted on AWS and delivered as a cloud application with no local install. That is one hosting arrangement with no region list, no customer environment option and no selection surface. The GDPR commitment is a privacy posture, not a residency option.

SourceRillet, rillet.com/product/security-and-permissions and info.rillet.comread 2026-09-07

Ember Agents arrive as a suite, each with its own job, across accounts payable, accounts receivable, transaction matching and categorization, transaction and accounting policy monitoring, accruals management and flux analysis, with close prep and board reporting on the checklist. A Migration Agent moves ledger history from a prior system, and Accounting Intelligence handles matching, uncategorized transactions, duplicates, accruals and prepaid amortization out of the box.

Sourcecampfire.ai/blog/introducing-ember-agentsread 2026-10-13

Rillet ships named specialized agents a customer puts to work on each workflow. A suite of specialized accounting agents covers flux, accruals, reconciliation and revenue, each scoped to one accounting workflow, alongside the Aura assistant and plain-English workflow agents. Each agent does its own job, so an accruals agent stays whole without the flux agent, and the agents ship as adoptable units inside the product, not as a pricing structure.

SourceRillet, rillet.com/product/aura-ai and rillet.com/product/security-and-permissionsread 2026-09-07

Coding and matching run on Accounting Intelligence, Campfire's own model built for accounting. Ember's chat runs on Anthropic's models, and OpenAI supplies language and embedding models for select Ember features and document reading, with neither provider training on the data sent to it. Campfire picks and routes between these models, and customers cannot choose or swap them. Reaching Campfire from Claude, Cursor or VS Code through its MCP server puts the customer's own assistant in front of the books, while Ember stays on Campfire's choice.

Sourcetrust.campfire.ai/?tab=subprocessorsread 2026-10-13

No model provider is named, and customers and admins have no choice of model. Under its model change management commitment Rillet manages its own model stack, with swaps flowing through Rillet's change controls, which is neither disclosed routing across providers nor a customer selection surface.

SourceRillet, rillet.com/product/security-and-permissions and rillet.com/product/aura-airead 2026-09-07

A REST API reference covers bank accounts and transactions, journal entries, bills, invoices, credit memos, revenue recognition contracts, bank reconciliations, files and financial statements, with create, update and delete endpoints. Access runs on API tokens or OAuth 2.0 apps with refresh tokens, optional PKCE and scoped permissions. The MCP server maps twelve tools to the API for Claude, Cursor and VS Code, all of them reads.

Sourcedocs.campfire.ai/llms.txtread 2026-10-13

There are two routes for calling the platform from outside. Through MCP, Aura connects to Salesforce, Snowflake, Claude or any BI tool with one secure surface for reads and writes, so an outside agent or tool can drive Rillet in both directions. A public API has documentation at docs.api.rillet.com with a getting-started guide.

SourceRillet, rillet.com/product/aura-ai and docs.api.rillet.comread 2026-09-07

A team can build a skill that tests Campfire's own output, such as one that ties every P&L total back to the general ledger and reports discrepancies, and confidence thresholds control what posts unreviewed. Both look at the books. Nothing lets a team score an agent or a skill against test cases before it runs on live data.

Sourcecampfire.ai/blog/standardize-close-process-ember-skillsread 2026-10-13

Nothing puts a change to the customer's agents under test. Under its model change management commitment, Rillet's own model swaps go through IT general controls with testing, approval and rollback under SOX 404, but that tests Rillet's release practice, not the customer's agents. Anomaly and error detection runs on the books, the customer's data, not the agent, and there is no harness, scored test set, live agent metric or release gate for the customer.

SourceRillet, rillet.com/product/security-and-permissions and rillet.com/product/aura-airead 2026-09-07

Ember works inside Campfire's ledger and reaches other tools through OAuth connectors, bank feeds and APIs, so no agent drives a browser or desktop application.

Sourcecampfire.ai/blog/campfire-is-the-first-erp-with-an-mcp-storeread 2026-10-13

The agents work inside the general ledger and through native integrations, syncing banks and processors and pulling data over connected systems. There is no browser, desktop or computer control operated by an agent, and no open research for each case at run time. The anomaly and flux work runs over the customer's own ledger data.

SourceRillet, rillet.com/product/aura-airead 2026-09-07