The offer
The client's technical person is welcome before a dollar is spent, and as often as they like after that. Under a nondisclosure agreement, they can see every result, ask any question, and run any of the checks below on the client's own system. Where a check needs an account, Siege provides one at the role the check calls for.
See it working
Guarantee | What to watch |
|---|---|
Every change is an action | Sign in as a role that may not take an action and try it. The system refuses, names the roles that may, and records the attempt. |
Agents are held tighter than people | Give a test agent one key. Ask it to do something else, and then to act where a business condition is unmet. It is refused both times, and both refusals are on the record. |
Every change is recorded | Change a value, then open the Records page and find the change with who made it, when, and the value before and after. |
The data layer sits apart from the software | Redeploy the software through the client's own pipeline while you watch. The data you checked beforehand, and its history, are unchanged afterwards. |
Nothing is lost silently when data moves | Watch a trial load of the client's own exported data. Every row that does not fit is held back with its reason, and nothing reaches live data until a person accepts the trial. |
AI drafts and people act | Open a screen with an AI draft. Nothing is saved or sent until a person does it, and with AI switched off the screen still works. |
Inspect the controls
Area | What to inspect |
|---|---|
Sign-in | The lockout after a few wrong passwords, the second step for administrators, and the record of sign-in attempts |
Sessions and cookies | Cookie attributes in any browser's developer tools; a role change ending a live session |
Transport | A public TLS test against the client's domain |
Isolation | The connection settings of the client's database, which serves the client's system alone |
Siege's access | Siege's Forward Deployed Engineer (FDE) account in the client's list of people, its sign-ins and every change recorded against it, and Siege's pull requests in the client's repository |
Backups | The backup schedule, and the record of the last restore test |
Your data | A full export from the Records page, opened in any spreadsheet or database tool |
Outbound connections | The list of every service the system talks to, and what crosses each one |
Questions
Every question gets a written answer. A page that turns out to be wrong is corrected in the next version of this documentation, and the correction is noted.