Security and governance. What your IT, risk and finance leads will ask.
Where the system runs, who can get in, how data and changes are handled, how AI is kept in check, and what you own at the end. Set out in the order a reviewer works through it.

- 01
Where it runs
In a cloud account your business owns.
- The system and its database live in your account, separate from every other client's.
- We work in it while we build. The account, and the data in it, stay yours.
- Nobody can lock you out of your records or change the terms on you.
- 02
Who can get in
Everyone signs in as themselves.
- Permissions follow roles, so each person sees what their job needs and nothing more.
- No shared logins are left behind, and access is reviewed as part of looking after the system.
- Integrations reach other systems with their own scoped credentials, never a person's password.
- 03
How data is protected
Encrypted, backed up and restorable.
- Data is encrypted in transit and at rest.
- Backups are taken automatically, and restores are tested.
- Records brought across from your current tools are checked against the originals.
- 04
How changes reach you
Reviewed, tested and recorded.
- Every change is reviewed and tested before it goes live, with a record of who changed what.
- The old and new systems run side by side. Nothing is switched off until your team has stopped using it.
- Dependencies are kept up to date and security fixes are applied promptly.
- 05
What gets recorded
Who did what, and when.
- Sign-ins and important actions are logged, so you can see what happened if something goes wrong.
- Automations and AI agents write every step they take to a log you can read.
- 06
AI under control
People approve what matters.
- Agents do defined jobs inside your own system, against your own records.
- Decisions you choose to keep, such as payments or large orders, wait for a person.
- Each agent reaches only the systems its job needs.
- 07
Ownership and exit
Yours outright, documented for whoever comes next.
- The intellectual property in the software we build is assigned to your business.
- You hold the source code in your own repository. Any capable developer can work on it.
- Each stage is scoped and priced before it starts, and you decide whether the next one goes ahead.
It lands in your account. Built by us, owned by you.
Data from the systems you already use arrives through a gateway into storage and a database inside your own cloud account, with the encryption keys held there too. Your dashboard reads it over a private link.
Questions to ask any developer. Including us.
Whose cloud account will the system and its data live in? How are logins, roles and permissions handled? How are backups taken, and when was a restore last tested? How are changes reviewed before they reach you? Who keeps the system patched after launch?
The full checklist, and where a custom system starts ahead of a shared product or behind it, is in Is custom software as secure as off-the-shelf?
Questions reviewers ask us
Where does our data live in a system Hypex builds?
In a cloud account the business owns. We work in it while we build, but the account, and the data in it, belong to the business.
Is a custom system harder to keep secure over time?
It needs looking after, like any software: updates, security fixes and access reviews. The difference from a subscription is that you decide who does that work, and you can see that it is being done.
What happens if we stop working with Hypex?
Nothing is taken away. The code, the data and the cloud account are in your name, and the system is documented so any capable developer can take it on.
Can our IT team or an outside reviewer assess the system?
Yes. Because the code and the infrastructure are yours, your own people or a reviewer you appoint can inspect both. Ask us for what your review needs and we will walk them through it.
Bring your reviewer.
Thirty minutes with the people who would build it, on how your system would run, who gets in, and what you own at the end.