The architecture behind Worktree, in plain language — not marketing gloss.
Every business on Worktree is a separate tenant at the data layer. Every record — every invoice, employee and product — is scoped to your client account and never visible to another business.
Permissions are granted per module, not all-or-nothing. Managers only see what their team and their assigned permissions allow — approvals in the Inbox are scoped to exactly who reports to them. Only an admin can change someone's roles or permissions.
Mark an employee Inactive and their access ends on their next click — every module and the AI assistant. Worktree also stops you deactivating the last admin who can sign in, so you can't lock yourself out.
Payments taken through the Payment Portal or at the till settle directly to your own connected Stripe account via Stripe Connect. Funds never sit with Worktree on their way to you.
Card processing runs entirely through Stripe. Card numbers are never entered into, or stored on, Worktree's own servers at any point.
Traffic to Worktree is encrypted end to end, and data at rest is protected with AES-256 encryption. GDPR-aligned handling applies across every module.
AI receipt scanning is rate-limited per user and capped by a global daily budget — a kill switch that stops the feature cleanly if usage spikes, rather than letting costs or exposure run away.
The questions we actually get asked before someone signs up.
Only people you've invited to your account, and only within the module permissions you've granted them. Worktree's data layer scopes every query to your client account — there's no cross-tenant visibility, by design.
No. Card entry and processing happen entirely inside Stripe's own secure checkout. Worktree never receives or stores raw card numbers.
Straight to your own Stripe Connect account, which you control and can withdraw from independently — the same way it would if you used Stripe directly.
An admin marks them Inactive. From their next request they're signed out of everything, with no waiting for a session to expire. Their records stay intact, and reactivating them restores their access.
They're sent to Google's Gemini API purely to extract the vendor, amount, VAT and category, and the request is rate-limited per user with a daily cost cap across the whole platform.
All card processing runs through Stripe — one of the most heavily audited payment platforms in the world.
PCI DSS compliant payment processing via Stripe. Your card details are never stored on our servers.
Every business connects its own Stripe account — payments taken through Worktree settle straight to it.
Talk to us directly — we'd rather answer it before you sign up than after.