Get in touch
Tell us about your firm and we'll be in touch within 48 business hours.
Request received
Thanks — someone from our team will be in touch within 48 business hours (Monday–Friday).
Check your inbox for a confirmation.
Obsidia runs on managed cloud infrastructure in Sydney — or, for organisations with the strictest data sovereignty requirements, inside a dedicated private AWS environment. Same product, same workflow packs, same audit trail. The choice comes down to where your data sits and which compliance frameworks you need.
Most private-sector firms run on the Standard Tier — modern managed infrastructure in Sydney that satisfies the Australian Privacy Act. Government, defence, and IRAP-regulated organisations run on the Compliance Tier — dedicated AWS infrastructure with full network isolation.
Each Standard Tier deployment is its own dedicated Supabase project and Netlify site — provisioned per client, never shared with another organisation. All data — documents, conversation logs, embeddings — is hosted in Sydney (ap-southeast-2) at rest and in transit. Generation runs on Anthropic Claude; retrieval uses Voyage AI embeddings.
It's the right choice for legal firms, accounting practices, professional services, and general enterprise customers who need reliable AI-powered search across their internal knowledge — without taking on the overhead of running infrastructure themselves.
voyage-3 (1024-dim) for retrieval. Neither vendor trains on your data.The Compliance Tier runs entirely inside a private AWS environment in Sydney — your own VPC, your own database, your own ECS services. The database has no public endpoint. All traffic flows through private subnets behind a managed WAF and CloudFront.
Both tiers give you a deployment that is yours alone — the difference is the infrastructure model. The Compliance Tier is the required choice for government agencies, defence, IRAP-assessed sectors, and APRA-regulated firms, and the right choice for any enterprise that needs physical network isolation and full penetration testing rights across the entire stack.
If you answer yes to any of the first three, you need the Compliance Tier. If you answer no to all of them, the Standard Tier is the right starting point.
Both tiers ship with the same product — the same chat experience, the same workflow packs, the same audit trail. The differences are at the infrastructure layer.
The deployment model is just the start. These controls apply to every Obsidia deployment regardless of tier — the things procurement and IT typically need clear answers on before sign-off.
Platform Admin, Admin, Workspace Admin, and Member roles — separating organisation-wide controls from workspace-level access from individual user permissions, so the right people see the right data.
Restrict platform access to specific IP ranges — your office network, your VPN, your designated remote-access service. Admin-configurable per organisation.
Onboard your entire team in a single CSV upload — no manual one-by-one user creation. Pairs with SSO (Azure AD) for streamlined provisioning at deployment.
A senior lawyer spending weeks building a "settlement position paper" prompt has encoded years of methodology into that text. An AMLCO crafting a suspicious-matter analysis workflow has embedded proprietary risk-scoring criteria. That content is your firm's IP. We make this commitment explicit — contractually, technically, and operationally.
Every prompt template, workflow configuration, and generated output you create on Obsidia remains your exclusive intellectual property. Our Terms of Service grant us only a narrow operational licence: store it, retrieve it, serve it to your users. Nothing more.
Your prompts are never used to train or fine-tune AI models, improve our product, build internal benchmarks, or run cross-customer analytics — not even in aggregated or de-identified form. This is contractual, not a setting you need to toggle.
Obsidia staff cannot read your prompt library. The only exception is a direct support scenario — a user-reported issue, with that user's explicit consent on record. Every such access is audit-logged and reviewed monthly.
When an employee leaves, their authored prompts stay with your firm — not their account. Authorship is updated to reflect the former employee; your workspace administrator can reassign it. Your firm's methodology doesn't walk out with a departing staff member.
Whichever tier you choose, Obsidia is built and supported as a production system from day one. Encryption at rest and in transit, audit trail on every query, no training of external models on your data.
Your data stays in Australia. Every deployment — Standard or Compliance — is provisioned for your organisation alone, never shared with another client.
That's not a feature — it's the foundation.