Security

Give AI accounting context without giving up firm control.

Firmwire keeps accounting credentials in the gateway, scopes work to authorized companies, and lets your team preview write workflows before approval. The goal is simple: advanced AI can help with the accounting workflow while the firm keeps access, review, and judgment.

Firm control

Keep control before anything is posted.

Firmwire gives approved assistants controlled accounting context while your team keeps ownership of access, review, and judgment.

Credentials stay server-side

Firmwire stores accounting credentials in the gateway. AI clients receive controlled access to workflows, not raw QuickBooks tokens.

Access follows authorized companies

Workflows run only against companies connected to the firm's workspace and available to the current user.

Changes wait for review by default

Journal entries, reclassifications, and record updates are held as a plan until your AI app sends an approval. Your app's tool-approval settings decide whether a person confirms it first.

For your vendor review

These controls support a firm's own safeguards. They don't make a firm compliant with any rule.

  • Sign-in. The login page offers an email magic link or Google, through Stytch. Multi-factor authentication is optional on new workspaces, and the owner can change the allowed sign-in methods in Settings.
  • Access. The workspace owner can use every connected QuickBooks company. Admins and members reach a company only after they're granted its connection.
  • Credentials. QuickBooks OAuth tokens are encrypted with AES-256-GCM, using a key derived from a Cloudflare Worker secret, and stored in Cloudflare D1. Traffic uses HTTPS, and every response sends Strict-Transport-Security.
  • Writes. By default, Firmwire holds each write as a plan and sends nothing to QuickBooks until the app sends an approval for that plan. Whether a person confirms that approval depends on the app's tool-approval settings. An app connected to the per-operation profile (/mcp?codemode=false) writes on the first call, with no Firmwire hold.
  • Activity record. Firmwire's activity log shows recorded operations and their outcomes, with the member, app, QuickBooks company, and approval state when they apply. It doesn't store the QuickBooks request or result. Recording is best-effort, so a logging failure doesn't block the call. Owners and admins can read the record with member and app names through the dashboard API, and connected apps in the workspace can read it by ID. In production, records become eligible for deletion 730 days after they're created, or 90 days after a deleted workspace's cleanup finishes.
  • AI. Firmwire returns each QuickBooks result to the app that requested it and doesn't send it to a model of its own. Pending write plans wait in a Cloudflare Durable Object.