Built to be checked — not taken on faith.
Before a Nexgile digital worker goes live, you can read its blueprint and rehearse it on synthetic data. With the optional red-team module, you can also test it against known attack techniques. This page shows how we prove it, and what we do not claim yet.
EU data protection
California privacy
In transit & at rest
Oversight & approvals
Security & availability
Top of the roadmap — target date: being finalized.
Information security
AI management system
Accessibility conformance
“In place” means the control or protection is active today. “Roadmap” means a formal third-party certification we are working toward. We never claim a certification before it is awarded. Contact security@nexgile.com for current status and documentation.
You’ll notice some chips say Roadmap. That’s deliberate. We publish what’s true today, not what we hope for, and we label claims across this site the same way. Top of the roadmap: SOC 2 Type II — target date: being finalized. Until those certifications are awarded, we offer the following. You run the software yourself, inside your existing compliance controls. You can read the audit-trail specification. Your security team can also review sample export files, with sensitive details removed, on request.
Security, engineered into every delivery.
Every export ships with its own security threat model, and we operate our own platform to enterprise standards.
- Encryption in transit and at rest
- Role-based access controls for the Studio and its workspaces
- A security threat model and data-flow diagram in every export
- Continuous monitoring, logging and a defined incident-response process
- Responsible-disclosure program for reporting vulnerabilities
Your data stays yours.
You design and test workers in the Studio. They can rehearse entirely on synthetic data, so you need no production data to evaluate them. After delivery, you host the software yourself, with no Nexgile cloud involved.
- Rehearsal can run entirely on synthetic data. No production data is needed to design or evaluate a worker
- You run the delivered software on your own infrastructure
- Data residency across our Herndon, VA and Hyderabad, India operations
- GDPR and CCPA aligned; retention and deletion on request
- Sub-processor transparency available on request
AI you can explain — and defend.
For an AI company, governance is a core responsibility, not fine print. Our foundation is built to make automated decisions accountable.
- Readable blueprints, not “the model decided”
- Business rules you state turned into fixed checks wherever possible. The same inputs always get the same verdict
- Approval steps that pause the worker until a person decides
- Every approval recorded, plus an optional tamper-evident run log. Specification available to your auditors
- Optional personal-data redaction when the worker uses its tools, off by default
Four mechanisms, built to be checked.
Every claim on this site rests on one of these. You can check each one yourself: in a live session, in a document your auditors request, or by replaying a past run. You don’t have to take any of it on faith.
Rehearsal before reality
The Studio generates realistic synthetic data for each worker's processes, so it rehearses real-looking work before touching a live system. Test it step by step or end to end, and watch test runs pause for approval and resume. Run many workers together, with time sped up if you wish, as simplified stand-ins by default or as the real workers. The optional red-team module tests a worker against known attack techniques. No production data is needed, so your security team can approve an evaluation based on your written description without a data-sharing agreement.
See it in Nx·StudioRules you can rely on
The AI analyst turns the business rules you state into fixed checks wherever it can, and flags any rule it couldn’t build in. A fixed check never calls an AI model, so the same inputs always get the same verdict. Routine decisions that nobody wrote down are the work of the Cognitive Engine, a separate product not built into Nx·Studio workers. It learns them from confirmed outcomes and acts only after passing an exam on cases it has never seen.
Meet the Cognitive EngineBlueprints you can read
Every digital worker is a versioned blueprint, not a tangle of prompts. It shows what the worker does, who approves what, and where it escalates. Every save is a version you can compare, merge or restore. The business reads it as swimlanes by team, person and system, and the Studio gives you a summary of exactly what was built. Like everything the platform generates, it is yours.
Governance you can readProof in every export
Every export includes a signed bill of materials: a list of every part of the software and its AI components. Your engineers can check it offline with the included verifier. The export also contains a security threat model and an EU AI Act documentation cross-reference. Separately, the Studio gives you an itemised ownership report. The worker is built to run without us: no Nexgile runtime, no license check, no metering and no calls home. “No lock-in” becomes something you can check for yourself.
Verify it yourselfDon’t take our word for any of this.
Every export comes with proof you can check yourself: a signed bill of materials, which lists every part of the software and its AI components. Your engineers verify it offline, on your own hardware, with no connection to us. The Studio adds an itemised ownership report. A sample, with sensitive details removed, is available on request. The verdict is yours to read.
The worker is built to run without us: no Nexgile runtime, no license check, no metering and no calls home.
Rules get the same treatment: we demonstrate them rather than assert them. In any live session, ask us to run the same case twice and see your stated rules return the same answer.
- Signed bill of materials every part of the software and its AI components, with a verifier that runs offlinein the export
- Threat model a security threat model and a data-flow diagramin the export
- EU AI Act cross-reference maps the Act's documentation items to the bill of materials — not a conformity assessmentin the export
- Ownership report an itemised list of everything delivered, plus a PDF summaryfrom the Studio
Verified on your hardware. The verdict is yours 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 documents you can read, compare version to version, and keep.
The blueprint is the audit artifact
Every worker is a readable, versioned blueprint. It sets out the worker’s agents and roles, connections, approval steps, routing and decision rules. Nothing is buried in prompts or locked in a vendor’s runtime. One document serves three audiences: your engineers version and compare it like code, your governance team reads it before deployment, and your auditors check against it afterwards.
Audit trails and lineage
Every approval is recorded on an audit trail: who approved what, and when. A tamper-evident run log and field-level data lineage (where each data field came from) are optional and off by default. Rules built in as fixed checks always give the same verdict for the same inputs.
The reviewer inbox is owned code
Human approval is built into the worker itself, as a reviewer inbox in the app. Slack, Microsoft Teams and email delivery are optional export settings. You choose who reviews each approval step, such as a role or a team. All of it ships as code you own: your approval policy is enforced in your software, not in a setting on our servers.
How we handle the data you choose to share.
Each worker can get realistic synthetic data generated for its own processes, so previews, simulations and red-team tests need no production data at all. If you choose to upload sample data instead, it is kept within your own workspace, and only its members can access it.
Material you share during design is treated differently. You may choose to share documents, process logs or sample data so your workers reflect your real volumes. You decide what to share, it is used only to design your workers, and a data-processing agreement is in place before anything moves.
An evaluation based on your written description shares no production data, only the description itself.
What gives the same answer every time, what doesn’t, and who decides.
Live AI judgment can vary from one run to the next.
That is why the rules you state do not depend on it. Wherever possible, they run as fixed checks inside the worker and return the same answer every time. You can replay a past test run step by step to confirm it. Routine decisions that nobody wrote down are the work of our Cognitive Engine, a separate product not built into Nx·Studio workers. It learns them from confirmed outcomes and acts only after passing an exam on cases it has never seen.
Where AI judgment is needed, a quality check can score its answer. You set the minimum score and choose what a low score does: flag it, stop the run, or send the case down another path, such as to a person. By default, it only flags. Approval steps pause the worker until a person decides.
Escalation is a control you set.
What your auditors can request.
Every artifact below is sanitized and shared on request — write to security@nexgile.com.
A sanitized blueprint excerpt
The swimlane view and export summary of a sample worker. Your governance team reads what a worker will do before it does it.
A sample evaluation report
Generated from a rehearsal on synthetic data. It is the document procurement teams ask for.
A sanitized export in miniature
The file structure, a runbook page, and a test-and-coverage report from a sample export. It shows what “production-grade” means in practice.
A redacted threat-model outline
What the threat model in every export covers, with configuration details removed.
The audit-trail specification
The events the audit trail records, and how the optional tamper-evident log reveals any later change.
A sample ownership report
The itemised list, signed bill of materials and verifier output from a sample export. The verdict is yours to read.
Your auditors can read what the worker will do before it does it.
Scoped on purpose. Kept on purpose.
One plain sentence each, limited to what the platform can prove. A specific promise you can verify is worth more than a broad one you cannot.
No production data is needed to design or rehearse a worker.
No vendor runtime. No per-decision fees to us. No calls home.
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 yet, we don’t publish it.
This rule covers other people’s numbers too. We quote third-party statistics only with their source and date. Our delivery counts carry a note on how we counted, and we re-check them before every publication. If we can no longer reproduce a figure, we remove it from the whole site.
Reliability
You run the software we deliver on your own infrastructure, so you control its availability, under your own service-level agreements. Our own platform is continuously monitored, with a defined incident-response process. A public status page for Nexgile services is on our roadmap.
Talk to the right team
- Security & disclosure security@nexgile.com
- Privacy & data rights privacy@nexgile.com
- Accessibility accessibility@nexgile.com