The standards, published before anyone asks for them.

Enterprise buyers are asked to trust claims that are difficult to verify. We would rather publish the standards we hold ourselves to, in plain language, and be measured against them.

Your data is yours, and only yours

Isolation between customers is a property of the design, not a configuration option that can be set incorrectly.

  • No shared record space between customers, by construction.
  • Access is granted by explicit authority, never inherited by accident.
  • Nothing about your operation is used to train anything for anyone else.

Everything is evidenced

Records are written as work happens, in tamper-evident form, so that proving what occurred is a query rather than a reconstruction.

  • What happened, who did it, when, and under whose authority.
  • What a record said at a past moment, not only what it says now.
  • One retention policy, stated, rather than six that disagree.
  • Evidence readable by the people who need it, without a specialist.

AI that is bounded on purpose

Six commitments. They constrain what we are allowed to build, which is the point of writing them down.

  • An AI never exceeds the authority of the person it acts for.
  • Anything financial or irreversible requires a human to confirm it.
  • Every proposal states what it read and why it concluded what it did.
  • Every action an AI takes is evidenced like any other action.
  • Your operational data is never used to train models for anyone else.
  • An operator can switch it off, per capability, without losing the system.

Accessible because it is required, not because it was requested

WCAG 2.2 Level AA is a build condition. A system used by shift staff, technicians and finance teams cannot be allowed to exclude the people who work for you, and retrofitted accessibility is both worse and more expensive.

This website is held to the same standard, and carries a full Accessibility Statement describing what we conform to, how we test, and what we know is imperfect.

How we know it is true

The foundations are built first.

Identity, permission, evidence and data shape are decided before the capabilities that inherit them.

Correctness is tested as a property.

Coherence between channels is asserted, not observed after the fact.

Accessibility is tested with assistive technology.

Keyboard and screen-reader paths are part of the definition of done.

Published standards constrain the roadmap.

If a capability cannot meet them, it waits.

Where we stand on certification

Orbitfy Inc. has not achieved SOC 2 certification, ISO 27001 certification, or certification under any other assurance scheme for Orbit. We will publish certifications on this website when they are held, with their scope and date.

Until then, this paragraph is the honest answer to the question, and it sits at full size on the page rather than in a footnote.

We are building this now.

Orbit is in active development. If you run a multi-site operation and this describes a problem you recognise, we would like to hear about it.

Get in touch