Procurement records get checked later: by an auditor, a regulator, a supplier in a dispute. So Atlas is built on one idea. Your records cannot be quietly deleted or changed, not even by your own administrators. Every action, including ours, goes into a log nobody can edit. The software enforces this. It is not just a policy.
The records and evidence behind a decision can't be deleted inside the product. Only their status changes, and every change leaves a trace.
Requisitions, orders, invoices, contracts and bids are never removed. They move through states. Suppliers are suspended. People are deactivated, and their past actions still show their name.
Enforced in codeOnce a requisition is approved, its documents are locked. A supplier's bid documents stay part of the competition record. An admin can't quietly remove them.
Enforced in codeRemoving a setting, such as an approval rule or a delegation, first saves the whole item to the sealed log. So you know who removed it, and it can be restored.
Enforced in codeEvery significant action goes into a log that can only be added to. The system can't change or delete it. Each entry is sealed to the one before it. Every hour, a checkpoint is stored off-site where it can't be rewritten. So editing one line, or replacing the whole log, gets caught.
Change entry 1,204 later, and its seal no longer matches. Every later entry was sealed using the one before, so they all break too. The database refuses edits and deletions outright. The hourly off-site checkpoint exposes even a full rewrite. We check the chain and its checkpoint on every backup restore.
Roles decide what each person can see and do. The riskiest action of all, removing an administrator, takes two people.
A requester can't approve their own spend. Only finance releases a payment. Access can be cut the moment someone leaves.
In productionApp-based (TOTP) two-factor can be required for everyone or just for admins. Passwords must meet a real strength policy.
In productionRemoving, deactivating or demoting an administrator needs a different admin to approve it first. One rogue or stolen account can't lock everyone out. The last admin can never be removed.
Enforced in codeAtlas Source to Pay was designed and built in Canada. Every workspace runs from our Toronto region today. The platform is not tied to one country. When a client signs, we set up a dedicated cloud instance in the region their data rules require.
Hosted in Toronto today. Traffic passes through Cloudflare's worldwide network. Encrypted backups are held by Backblaze. A dedicated instance in your own region is possible by separate agreement.
In productionEvery company gets its own separate database. One customer physically cannot read another's. That separation is by design, and our own attack testing checks it.
In productionThe whole data volume is encrypted at rest. Bank details and secrets get extra field-level encryption, with keys kept outside the database. TLS and HSTS in transit.
In productionA backup nobody has restored is a hope, not a backup. So we prove ours, and lock them where ransomware can't reach.
A full snapshot every hour, also sent off-site. Each one is opened and checked as it is taken.
In productionA copy goes to a second, independent provider. It is encrypted before it leaves and locked so it can't be changed or deleted, even with a stolen key.
In productionEvery company’s database is copied as it is written, second by second, to encrypted storage. A mistake inside the system costs about a second. Losing the whole server costs about five minutes.
In productionWe regularly restore a backup, open it and check the audit chain. We can restore one company’s data without touching anyone else’s.
In productionWhat you put into Atlas stays your record, under your control. Kept intact, kept private, and yours to take.
Records and evidence can't be destroyed or rewritten inside the product. These protections are enforced, not promised.
Kept separate for each company. Encrypted at rest and in transit. Sent off-site only in encrypted form a third party can't read.
An administrator can export the whole workspace to open CSV files any time, from inside the product. Returning or deleting your data is clean and complete.
Trust is easier to give when the limits are named, not hidden.
The questions a security review asks, answered straight, including where the answer is a limit. The evidence sheet shows how to check each one.
Ransomware, breaches, retention, sub-processors. Ask directly, and we'll show you how it works, not a slide.
Book a demo