We only ship what survives our own attacks.
Before a Nexgile digital worker goes live, you can read its flowchart, it has been tested on realistic data, and it comes with a security risk assessment and a list of what's inside. This page is how we prove it.
EU data protection
California privacy
Data sent and stored
People approve key steps
“In place” means active today. Contact security@nexgile.com for documentation.
Security, built into everything we deliver.
The software Nexgile generates comes with security built in — and we run our own platform to enterprise standards.
- Encryption for data that is sent and stored
- Access controls that give each person only the access they need
- A security risk assessment with every downloaded worker
- Round-the-clock monitoring, activity logs and a clear plan for handling security incidents
- A program for reporting security flaws to us safely
Your data stays yours.
Nx·Studio is a design-and-test studio: each worker can be tested on sample data made just for it, so you don't need real records to evaluate it. After delivery, you run it yourself — no Nexgile cloud is involved.
- Testing runs on generated sample data by default — uploading your own data is your choice
- You run the delivered software on your own systems
- Data kept within our Herndon, VA and Hyderabad, India operations
- GDPR and CCPA aligned; retention and deletion on request
- A list of the outside companies that handle data for us (sub-processors), on request
AI you can explain — and defend.
For an AI company, governance is a core concern, not fine print. Our foundation is built so automated decisions can be explained and checked.
- Readable designs — rules and approvals you can see, not “the model decided”
- Rule steps that give the same answer for the same facts, with no AI involved
- Approval steps designed into every worker — a run waits for a person
- A step-by-step record of every test run — and, in downloaded workers, an optional log that shows if anyone changes it
- Each customer's data kept separate inside the database
Four principles, built to be checked.
Every product claim on this site stands on one of these. Each is something you can check — in a live session, in a document your auditors request, or in the code itself — not something you are asked to take on faith.
Tested before it's trusted
Every worker gets its own realistic sample data, so it can be tested before it touches a live system — on the same engine you'll run. Every run is recorded step by step: what went in, what came out, who approved and what each AI step cost. Compare versions side by side, and let a statistical test pick between alternatives. Because the data is generated, your security team can approve an evaluation without handing over real records.
How testing worksRules that run as rules
Rules you write in plain English become real steps inside the worker. So “refunds over $10,000 need the finance director's approval” is a step that runs — not a sentence in an AI prompt that a clever message could talk around. Rule steps don't use AI, so the same facts always get the same answer. The Cognitive Engine goes further: it learns routine decisions from confirmed outcomes and makes them without AI, but only after passing an exam.
See the Cognitive EngineBlueprints you can read
Every digital worker is a flowchart you can read, not a tangle of AI instructions: what it does, who approves what, and when it asks a person. Every change is saved as a new version you can compare. A health check runs before download, and steps that could change or delete data without an approval are flagged. So your auditors can read what the worker will do before it does it.
Governance you can readCode you own
Every download is the complete code of the worker and the engine it runs on — with no license key, nothing to rent and no connection back to us. Your engineers can read every line. Each download also includes a security risk assessment and a signed list of everything inside, so “no lock-in” is something you can check, not something you take on trust.
Check it yourselfDon't take our word for any of this.
Every download is the complete code — the worker and the engine it runs on. Your engineers can check it themselves, on your own computers, for anything that depends on Nexgile, connects back to us or checks a license.
Each download also comes with a security risk assessment and a signed list of everything inside.
Rules get the same treatment — demonstrated, not asserted. In any live session, ask us to run the same input through a rule step twice and watch it land on the same answer.
- Dependencies anything that needs a Nexgile service to runcheck
- Connections to us anything that contacts Nexgilecheck
- License checks license keys or activation stepscheck
Your hardware, your engineers, your verdict — the code is all there to read.
Your auditors read what a worker will do before it does it.
Governance here isn't a dashboard over a black box. It's a set of files you can read, compare and keep.
A blueprint your auditors can read
Every worker is a blueprint you can read: its AI agents and roles, connections, approval steps, paths and decision rules. Nothing is hidden in AI prompts or locked inside someone else's platform. One document serves three groups: your engineers track and compare its versions like code, your governance team reads it before it goes live, and your auditors check against it afterwards.
A full record of every decision
Every run is recorded step by step: which version ran, which rule or AI step acted, who approved what, and when. Downloaded workers keep the same record, and can add a sealed log that shows if anyone changes it later. Rule steps always give the same answer for the same facts.
Approval is a step in the code
Approval steps are part of the worker's design and of its code: the worker stops until a person decides. So your approval rules live in software you own, not in a setting on our servers.
How we handle the data you choose to share.
Each worker can be tested on sample data made to fit it, so test runs don't need real records. If you choose to import your own data, it stays walled off for your organization.
Materials you share for the design are different, and we treat them that way. If you choose to share documents, existing automation scripts or system logs so your workers reflect your real volumes, you decide what to share. It's used only to design your workers, and a data-processing agreement is in place before anything moves.
Share a description of your business process. We evaluate the workers using generated sample data — no production data is required.
What always gives the same answer — and what doesn't.
AI steps can give different answers on different days.
That's why the rules you write become rule steps: same facts, same answer, no AI involved. It's also why the Cognitive Engine only takes over a routine decision after passing an exam on cases it has never seen.
Where judgment is genuinely needed, an AI step does the work — and wherever a person must decide, the design adds an approval step where the worker waits.
An approval isn't a courtesy. It's a step.
What your auditors can request.
Every document below has sensitive details removed, and is shared on request — write to security@nexgile.com.
A sample blueprint, with sensitive details removed
Shown as a readable document — your governance team reads what a worker will do before it does it.
A sample test report
From a studio test run on generated data — every step, what went in and out, and every approval.
A sample download
The files of a downloaded worker, its start scripts and its test — what you actually receive.
A sample security risk assessment
The one that comes with every download — with sensitive details removed.
How workers record what they do
The step-by-step record every worker keeps, and the optional log a downloaded worker can add that shows if anyone changes it.
A sample list of what's inside
The signed list of AI models, software libraries and data inside a download.
Your auditors can read what the worker will do before it does it.
Promises we can keep.
One plain sentence each — limited to what the platform can prove, because a careful promise beats a sweeping one.
You can evaluate a worker entirely on generated data — your real records are never required.
Nothing to rent. No per-decision fees. No connection back to us.
Nothing stops working if you stop paying us.
Every number on this site comes with how we measured it. When we can't measure something honestly, we don't publish it.
The house rule covers other people's numbers too: we show them only as quotes, with their source and date. Our delivery counts come with a note on how they're counted, and are re-checked before every update. Figures we can no longer reproduce are removed from the whole site — not quietly kept.
Reliability
Because you run the software we deliver yourself, keeping it available is in your hands — on your own systems, to your own standards. Our own platform is monitored around the clock, with a clear plan for handling incidents.
Talk to the right team
- Security & disclosure security@nexgile.com
- Privacy & data rights privacy@nexgile.com
- Accessibility accessibility@nexgile.com
You describe it. You test it. You own it. You run it.
Bring your security, risk, and compliance teams. An evaluation can run entirely on generated data — your security team doesn't have to hand over real records to say yes.