Hosting and security

Your own system, in the EU.

Every firm has its own copy of Orca and its own database, in the EU: in Frankfurt today, in Sweden once Azure runs. Written for whoever looks after your IT: every answer, without a meeting.

Get started
Last reviewed 17 Oct 2026
The short answers

Eleven questions, answered first.

The short answers
Hosting

Where it runs. Today, and where it goes.

Today every firm runs in Frankfurt, in the EU. Azure in Sweden is the target and does not run yet. Later a firm picks shared or its own installation, and Orca runs both.

Where it runs todayToday
Where
Frankfurt, in the EU, on Fly and Neon. Each firm has its own app and its own database.
State
Running. A firm that starts now is moved to Azure in Sweden when that runs.
SharedPlanned
Where
Azure in Sweden. Each firm keeps its own copy and database, on servers shared with other firms. A copy sleeps when idle.
State
The default, and not built yet. An independent review of the separation comes before the first real firm is on it.
Its own installationPlanned
Where
Azure in Sweden, in the firm’s own account or one Orca holds. The firm pays its cloud at cost, and one more Care at its size’s price.
State
For a firm whose IT wants it, and not on Azure yet. Orca runs it, from a compiled image that checks its licence; the source stays with Orca.
Where it runs todayToday
SharedPlanned
Its own installationPlanned
Account
YouOrca
YouOrca
YouOrca
Run by
YouOrca
YouOrca
YouOrca
Where
Frankfurt, in the EU, on Fly and Neon. Each firm has its own app and its own database.
Azure in Sweden. Each firm keeps its own copy and database, on servers shared with other firms. A copy sleeps when idle.
Azure in Sweden, in the firm’s own account or one Orca holds. The firm pays its cloud at cost, and one more Care at its size’s price.
State
Running. A firm that starts now is moved to Azure in Sweden when that runs.
The default, and not built yet. An independent review of the separation comes before the first real firm is on it.
For a firm whose IT wants it, and not on Azure yet. Orca runs it, from a compiled image that checks its licence; the source stays with Orca.
Where it runs todayToday
Where
Frankfurt, in the EU, on Fly and Neon. Each firm has its own app and its own database.
State
Running. A firm that starts now is moved to Azure in Sweden when that runs.
SharedPlanned
Where
Azure in Sweden. Each firm keeps its own copy and database, on servers shared with other firms. A copy sleeps when idle.
State
The default, and not built yet. An independent review of the separation comes before the first real firm is on it.
Its own installationPlanned
Where
Azure in Sweden, in the firm’s own account or one Orca holds. The firm pays its cloud at cost, and one more Care at its size’s price.
State
For a firm whose IT wants it, and not on Azure yet. Orca runs it, from a compiled image that checks its licence; the source stays with Orca.

Swipe for all three.

Isolation

Every firm on its own. Its own copy, its own database.

Your firm has its own copy of Orca and its own database, also on servers shared with other firms. Its own key covers its files, backups, exports, secrets and named sensitive fields. The database server’s own encryption is shared.

No query, index or agent memory spans two firms.

Built in
  • People and roles, set by your firm
  • An audit trail of every change
  • Backups, monitoring and rollback, run by Orca as part of Care
  • Every connection listed in Settings, ours included, to pause or revoke
Assurance

What we sign, test and certify. And what isn’t done yet.

Data processing agreementWe’re your processor under GDPR, and sign the agreement before any personal data reaches us. Our security policy and sub-processor list come with it.Every client
Independent reviewAn outside party reviews how firms are kept apart before the first real firm is on a shared server. Tests that try to reach another firm’s data run in every release.Planned
Reviewed buildsAI helps us write the code. Every release runs through tests and type checks, and anything that decides who sees what, or touches money, gets a separate independent review before it ships.Every build
Scanning and sign-offEvery change is scanned for known weaknesses, exposed secrets and risky code, and an engineer signs off every build before it ships.Planned
NIS2Covered by the Cybersecurity Act (NIS2)? Your supplier requirements go into our agreement, and we answer your supplier questionnaire.Every client
ISO 27001Orca is not certified yet. Where it stands is just below.Planned
ISO 27001
Not certified yet. Here is the plan.
Now · What every client gets
A security policy, the data processing agreement and the controls on this page. Every release runs tests and type checks, with an independent review of the sensitive parts.
Next · Within our first year
A gap analysis against ISO 27001, and a fix for every gap it finds.
Then · In our second year
Certification by an accredited body.
  1. Now · What every client gets
    A security policy, the data processing agreement and the controls on this page. Every release runs tests and type checks, with an independent review of the sensitive parts.
  2. Next · Within our first year
    A gap analysis against ISO 27001, and a fix for every gap it finds.
  3. Then · In our second year
    Certification by an accredited body.

Status on 17 Oct 2026: Orca is not ISO 27001 certified. These are plans, and this page changes when they do.

The code

Your data goes with you. The code outlives Orca.

The code is not published. A third party holds the source and releases it to your firm if Orca ceases to exist. Leaving is simple: take your data out, any day.

Leaving is simple: take your data out, any day. The right to use the installation ends with Care.

What goes with you
Ready any day
  • Your dataAll of it, in open formats.
  • Your filesDocuments and attachments.
  • Made-for-you rowsEvery row that work holds or produced.
  • Brief and specificationWhat you paid for, to take to anyone.

At no cost, whether you stay or leave.

AI

The models we use, and where they run.

One gateway

Every call to a model goes through one gateway that records the model, provider, region and cost. The providers are named in our sub-processor list; you hear from us before it changes.

The right model for the job

Small, efficient models ask the interview questions; a stronger one helps draft the analysis. People at Orca read and check all of it.

EU-hosted, unless you choose otherwise

Models run on servers in the EU, and only leave it if you ask us to. No provider may train on your data.

Discovery interviews

What your people tell us stays where it should.

When your firm orders a Blueprint, the people you choose each give a 15-minute interview from a link, typed or spoken. Each person sees what is kept, for how long and who reads it, and agrees before anything is stored.

How long it’s kept
90 days
Voice recordingsDeleted 90 days after the Blueprint is signed.
12 months
TranscriptsDeleted 12 months after go-live.
7 years
The signed BlueprintKept 7 years after the contract ends, as a contract record, with quotes by role.

Our defaults, shorter on request. Anyone can stop, or have their answers deleted, at any time.

Where it’s kept
In your firm’s own workspace at Orca, in the EU.
Who reads it
Orca’s team reads the answers, transcripts and recordings. Your firm sees only our analysis: every quote carries a role, never a name, unless that person agrees.
Outside the EU
Nothing leaves the EU unless you ask for it. If you do, only under our data processing agreement and the EU’s rules for transfers.

Everything here, in writing.

The data processing agreement, our security policy and the sub-processor list, before you sign anything.

Get started