Built to pass the review your IT lead will give it.
This page is for the person who has to sign off on us. It covers how the system decides what to do, how it proves what it did, how each company's data is kept apart, and what we'll do when your industry asks for more.
It proposes. A person decides.
Most AI tools your staff try this year will act first and log later. Vowric is built the other way round. Nothing leaves the system on its own initiative: no email to a customer, no message, no booking, no invoice, no price. The system drafts, and one of your people approves. That isn't a setting someone can switch off, because it was never a setting.
The original is never overwritten by what we make of it. The call, the email and the voice memo stay exactly as they arrived, whatever is proposed or declined on top of them. What was said is shown apart from what the system inferred, so nobody mistakes a guess for a fact.
approved by: dispatch, 07:51, before sending
because of: "the cooler at the Markham site is running warm"
landed: delivered 07:51:12
Each company's data is kept apart by the database itself.
Isolation between customers is enforced underneath the application, where a mistake in our own code can't reach past it. A query that forgets which company it is for returns nothing, never somebody else's records.
| Mechanism | What it means for you |
|---|---|
| Forced row-level securityon every company's tables | The database refuses an unscoped query, even from us. |
| One enforcement chokepointfor every scoped read and write | Authority is decided in a single place, so there is a single place to audit. |
| Declarative authority manifestversioned, immutable per version | Who may do what is data you can read and compare, pinned to the version that was running. |
| Row scope at the databaserestrictive on read | Narrowing someone's access doesn't depend on every screen remembering to. |
| Append-only auditactor, source, destination | The record of what happened is kept apart from what the software says it did. |
| Cross-company isolation testsagainst a real database | Leakage between customers is a test that must pass before every release. |
| Full export, on demandopen formats, whole record | If you leave, you leave with everything: the originals, the history and the audit trail. |
| One credential per instanceencrypted at rest, every use logged | A compromise anywhere reaches exactly one host, and every use of a secret records who asked and why. |
Multiple locations run on one install, under one company, and each person sees the records they're connected to.
Identity and access
- Passkeys, Google and Apple sign-in, and email linksno shared passwords on the shop floor.
- Roles per locationowner, manager, dispatcher, staff, client, each scoped to the records they're connected to.
- Field-level permissionsa technician can log hours without seeing the invoice.
- Active sessions and sign-out everywherefor a lost phone at 6 a.m.
Integrations
- Scoped, rotatable keysfor each integration and each AI agent you connect, never one master key.
- Your accounting systemfed directly, in the format it reads: QuickBooks today.
- Your mailboxesconnect the inboxes you already have; messages file themselves on the right record.
- Bank and card statementsimported and matched to the ledger, every match explainable and reversible.
- Migration inyour existing records brought across; what can't be read is reported, never quietly dropped.
Reliability
- Nightly encrypted off-site backups, restore-testedA backup nobody has restored is a rumour. Ours are proven by restoring them.
- Durable background jobs with stuck-job recoverywork that's queued gets done, or is named as failed.
- Monitoring across every machinea failed check pages us, and every miss is kept in the history.
- Data locationon request, place by place, including backups and every provider.
When your industry asks for more
If your work requires SOC 2, ISO 27001, HIPAA, Ontario's PHIPA or PIPEDA, tell us at the start. We scope the controls, the evidence and the audit into the engagement, and put the platform through the review. The audit trail, the database-enforced separation and the restore-tested backups are already the kind of evidence those reviews ask for.
Security details for your review are available on request: write to [email protected] and we'll answer your questionnaire directly. Visit the trust centre.
Tell us how your company runs.
How your company runs today, what keeps getting dropped, and what you run it on. We'll reply about an operations map.
- email[email protected], and a person replies
- phone+1 289 806 5300, answered at any hour, and a person follows up
- where we areThe Greater Toronto Area, Ontario