Your data, your decisions, your code.
This is where security, risk and compliance teams can check how Nexgile works: how workers are tested, who approves what, how to verify an export, and which certifications we hold today and which are still on our roadmap.
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” reflects controls and protections active today. “Roadmap” marks formal third-party certifications we are actively pursuing — we do not 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, not what’s aspirational — and every claim on this site is labeled the way we label these. Top of the roadmap: SOC 2 Type II — target date: being finalized. While certifications are in flight, here’s what we offer today instead: workers you run inside your existing compliance boundary, audit-trail details, and sample export artifacts your security team can review on request.
Security, engineered into every delivery.
The software Nexgile generates ships with security built in — and our own platform is operated to enterprise standards.
- Encryption in transit and at rest
- Identity and access controls with least privilege by default
- A security threat model, with a 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.
Nx·Studio is where workers are designed and tested, on synthetic data generated for each one, so no production data is needed to evaluate them. After delivery, you run the workers yourself, and they never call back to Nexgile.
- Workers are tested on synthetic data; you decide if and when to share sample data of your own
- 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 first-class concern, not fine print. Every worker is built so its decisions can be read, tested and explained.
- Readable blueprints: see every step, rule and approval before a worker runs
- Rule steps give the same result for the same input, every time
- Approval steps pause the worker until a person approves, rejects or edits
- Every test run traced step by step; audit-trail details available to your auditors
- You choose the AI provider and model, using your own API keys
Your code stays between you and your AI provider.
Nx IDE runs on your machine. There's no Nexgile cloud in the middle and no usage telemetry: your code goes only to the AI provider you choose, or nowhere at all with a local model.
- No usage telemetry
- Code goes only to the AI provider you choose
- Local models through Ollama or LM Studio
- License key checked offline, on your machine
- Asks before edits, commands and tool calls by default
- A TAA edition without China-based providers
Four things you can check for yourself.
Every claim on this site rests on one of these. You can see each one in a demo, in a sample your auditors request, or in the code you receive.
Synthetic-data rehearsal
Every worker is tested in a sandbox on synthetic data generated for it, like the invoices, claims or tickets it will handle. Built-in scenarios cover missing fields, oversized inputs, unclear requests and failures, every step of every run is traced, and you can compare two versions on the same scenario before changing anything. Your security team can approve an evaluation that starts from a description, with no data shared.
See how workers are testedRules that run as rules
The business rules you describe become rule steps that run as plain code, so a clever prompt can't talk them out of policy and the same input always gets the same decision. AI handles only the unclear parts, and each worker's readiness score shows how much of it runs on rules.
Watch a worker sort a morning's workReadable blueprints
Every digital worker is a readable, versioned blueprint, not a tangle of prompts: what it does, who approves what and where it escalates. Compare versions when policy changes and hand them to your auditors before deployment. The exported code runs that same blueprint file, so what your reviewers read is what runs.
Governance you can readOwnership you can verify
Every export is the complete application, with no Nexgile runtime, license check, meter or call home inside, and your engineers can read every line to confirm that. Each export also carries a signed bill of materials and an offline script that checks the package is exactly what was generated. “No lock-in” becomes something you check, not a slogan.
Verify an export yourselfDon’t take our word for any of this.
Every export is the complete application, with no Nexgile runtime, license check, meter or call home inside. Your engineers can read every line to confirm that.
Each export also carries a signed bill of materials and an offline verification script. Run the script on your own machine to check that the package is exactly what Nx·Studio generated. A sample run is available on request, and the result is yours to read.
Rule steps get the same treatment: shown, not asserted. In a demo, ask us to run the same scenario twice and watch the rule steps give the same answers both times.
- checkSigned bill of materials every component in the package, listed and signed
- checkOffline verification script confirms the package is exactly what was generated
- checkReadable source code no Nexgile runtime, license check or calls back to Nexgile
Runs offline, on your own hardware. The result 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 things you can read, compare and keep.
Read the blueprint first
Every worker is a readable, versioned blueprint of its AI steps, rule steps, approval steps and connections, not a tangle of prompts. Your engineers compare versions like code, your governance team reads it before deployment, and the exported code runs that same file.
Every step traced
In Nx·Studio, every test run is traced step by step: each decision, tool call and cost, and which version of the worker ran. Rule steps give the same result for the same input, and a clever prompt can’t talk them out of policy. What exported workers record.
The reviewer inbox is your code
When a worker has approval steps, its export includes a reviewer inbox app, with multi-person sign-off, no approving your own request, and optional Slack, Teams or email notifications. It ships as code you own, so your approval rules live in your software, not in a setting on our servers.
How we handle the data you choose to share.
Workers are tested in a sandbox on synthetic data generated for each one, built from a model of the records it handles. You decide if and when to import sample data of your own.
Documents you choose to share, like policies, forms or process maps, are treated differently: you decide what to share, it’s used only to design your workers, and a data-processing agreement is in place before anything moves.
A description-based evaluation shares nothing at all.
What’s fixed, what isn’t, and who decides.
AI judgment can vary from one run to the next.
That’s why workers use as little of it as possible. The rules you describe become rule steps that run as plain code, so the same input always gets the same answer, and you can test that on the same scenario as often as you like.
Where judgment is needed, you decide where people come in. Approval steps can send a case to a person, for example when the AI’s confidence is low or an amount is high, and the worker waits until someone approves, rejects or edits.
Escalation isn’t a courtesy. It’s a control.
What your auditors can request.
Every sample below is sanitized and shared on request. Write to security@nexgile.com.
A sample blueprint
A worker's blueprint rendered as a readable document, so your governance team can see what a worker will do before it does it.
A sample evaluation report
The report Nx·Studio produces from a test run on synthetic data: accuracy, speed, cost, safety, robustness and coverage.
A sample export
The file tree, README and test results from a sample worker's export, so you can see what you'd receive.
A sample threat model
The security threat model and data-flow diagram that ship with every export, from a sample worker.
Audit-trail details
What a worker records about each run, step by step, and the optional tamper-evident audit log you can switch on at export.
A sample verification run
The signed bill of materials and the offline verification script's output for a sample export. The result is yours to read.
Your auditors can read what the worker will do before it does it.
Three promises, kept on purpose.
One plain sentence each, limited to what the product can show you.
Every worker is tested on synthetic data before it touches a live system.
No Nexgile runtime. No per-run fees. No calls back to Nexgile.
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.
The house rule covers other people’s numbers too: third-party statistics appear only quoted, attributed, and dated. Our delivery counts carry a method footnote and are re-verified before every publication. And figures that stop reproducing are retired sitewide — not quietly kept.
Reliability
Because you self-host the software we deliver, its availability is in your hands — on your infrastructure, under your SLAs. 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
Bring your security team to the demo.
Demos run on synthetic data, so there’s nothing to share up front. Bring your security, risk and compliance teams with their hardest questions.