What stays inside your boundary
NeoAI, the recipe store, the evaluation harness and the audit log all run inside your cloud boundary. Your apps call your existing AI gateway, NeoAI sits behind it, and NeoAI calls your model providers. Adopting NeoAI adds no new data, integration or financial risk: it is one endpoint change, with no workflow change.
Security and ownership commitments
| Area | What NeoAI commits to | Status |
|---|---|---|
| Deployment | Runs in your VPC, behind your existing AI gateway | Commitment |
| Data use | Prompts never train anything for other customers | Commitment |
| Recipe ownership | Recipes are owned by you and exportable | Commitment |
| Auditability | Every recipe version is logged and auditable | Commitment |
| Reliability | Automatic fallback: a failed step escalates, and the user never sees an error | Commitment |
| Data processing agreement | DPA available | Available |
| SOC 2 / ISO 27001 | Certification plan to be shared with your security team | To be confirmed |
How quality is protected before go-live
Quality is tested before go-live on your own prompts against your acceptance criteria. The evaluation method is open to your team, so your engineers can inspect the evaluation set, the acceptance rules and the results rather than take a score on trust. See how the pilot is structured.
Questions your security team will ask
- Does data leave our cloud? NeoAI is designed so that it does not. Confirm the exact data flows with us in the audit.
- Can we leave and keep what was learned? Yes: recipes are yours and exportable.
- Can we see what changed and when? Yes: every recipe version is logged.
- What certifications do you hold? The certification plan and status are still to be confirmed, and we will say so plainly in any security review.
To start a security review, email contact@neoai.solutions or request the free audit.