Questions, answered.

Capallo is a treasury governance OS — the operating layer that sits between your treasury team and the systems they already use (TMS, ERP, banks). Every recurring treasury decision (FX, debt, liquidity, payments) becomes a controlled workflow with policy enforcement, approval routing, evidence capture, and an audit-ready output. We are the system of record for the decision process, not the ledger or payment rail.

Capallo is built for mid-market to upper-mid-market corporate treasury teams — typically AUD $50M to $2B in revenue — where treasury decisions have material consequence but governance still lives in spreadsheets, Slack threads, and an annual audit scramble. We're also a fit for advisory and accounting firms governing treasury operations for multiple corporate clients — see For Advisory Firms.

TMSs handle execution and reporting — they're systems of record for the transactions themselves. Capallo sits one layer up: we govern the decision before it happens. Policy checks, delegated authority, segregation of duties, evidence capture, and the audit trail are all native to the workflow, not bolted on after the fact. Most customers run Capallo alongside an existing TMS rather than replacing it.

Capallo's primary production environment is hosted in AWS Sydney (ap-southeast-2). Customer workspace data stays in that region by default. We can discuss specific data residency requirements during onboarding — full detail is on our Security page.

Not yet. We're targeting SOC 2 Type I in Q1 2027 and have a compliance automation platform being procured to support the audit. Current controls, encryption posture, and the full certification roadmap are documented on our Security page.

Capallo is designed to be system-of-record-agnostic. Phase-1 priority integrations are the major Australian banks (CBA, ANZ, NAB, Westpac, HSBC) and the mid-market ERPs (NetSuite, Xero, MYOB). Specific connector readiness varies by quarter — happy to confirm what's live for your stack during a conversation.

We're not publishing fixed price points while in early access. Pricing is structured around the number of decision families you enable, workspace count, and integration depth. Charter Partner pricing for the early cohort is significantly discounted in exchange for design-partner feedback. Pricing detail comes on the first call.

A small cohort of design partners that gets Capallo at deeply discounted pricing in exchange for: weekly feedback during onboarding, willingness to be referenced privately to other prospects, and a committed go-live timeline. Charter Partner status closes once the cohort is full — typically the first 6 customers.

Yes — that's exactly what our advisory partnership is built for. Firm-led, multi-tenant deployment with one firm console across every client engagement and isolated client workspaces underneath. Full white-label (custom domain, custom branding) is a roadmap item we can discuss for Charter Partners with the right scale. See For Advisory Firms for the full breakdown.

Initial workspace setup with one decision domain enabled: typically 1-2 weeks. Adding policy authoring, delegated authority matrices, and a second domain: another 2-3 weeks. Most teams reach steady-state operation in 4-8 weeks for the first domain, with each subsequent domain rolling out faster as your team builds policy authoring fluency.

Most customers do, and Capallo is designed to coexist. Your TMS keeps doing what it does (execution, position keeping, reporting). Capallo handles the decision governance layer — policy, evidence, audit trail — that TMSs don't cover deeply. The common pattern: Capallo upstream of the TMS for decisions, the TMS for execution.

Book a conversation — 45 minutes with the founder. We walk through Capallo end-to-end and figure out whether you're a fit for the Charter Partner cohort or a later production cohort.