Bridge Town runs in Claude, Codex, Cursor, and any MCP client.
One install, four agents, same answers. Your team picks the surface they're already in. The model is the source of truth.
Bridge Town turns financial models into a version-controlled codebase your agent can read, run, and review. Every change is controlled, tracked, and tested.
Open Claude with Bridge Town pre-configured as a connector. OAuth — no tokens to copy. Chat seamlessly across desktop, web, and mobile in the same session.
Bridge Town isn't a wrapper around a spreadsheet. It's a financial modeling platform where every assumption is code, every scenario is a branch, and every actual is a commit.
One install, four agents, same answers. Your team picks the surface they're already in. The model is the source of truth.
Branch, propose, review, merge. The merge gate is the EBITDA delta — not "looks good to me."
Side-by-side variance, line-by-line driver attribution, one-click rollback to any prior month-end snapshot.
Bridge Town vs Anaplan comparison · Bridge Town vs Pigment comparison · Bridge Town vs Excel comparison · Bridge Town vs Google Sheets comparison
Every number traces to the commit, the scenario, the input source, the analyst. Auditors stop asking; you stop screenshotting.
From an empty workspace to a model your agent can query — fast enough to do during a stand-up.
Click Connect to Claude, or paste the install command into Codex, Cursor, or OpenCode. OAuth in one window.
"Build a 3-statement model for an SaaS company doing $40M ARR, 110% NRR, 65% gross margin." Your agent generates the Python through Bridge Town MCP tools; Bridge Town runs it sandboxed and shows the result.
Open a PR for next quarter's headcount plan. The reviewer sees the EBITDA delta, the driver-level attribution, and the run log — before they hit merge.
Connect Bridge Town to the agent your team already lives in. Free for your first workspace; production teams scale to seats.
Bridge Town is built for finance teams who can't afford a leak. Encryption at every layer, scoped access for every agent, and an audit log that reads like git history — because it is git history.
TLS enforced on every wire. AES-256 on every disk. Per-workspace data keys in AWS KMS, rotated quarterly.
Every agent connection uses a workspace-scoped token tied to a single account. Tokens carry the issuing user's permissions and are revocable from the dashboard at any time.
Models, runs, and scenario edits land as commits in an append-only log. Every number traces to a commit, a scenario, an input source, and an analyst.