NeoAI
Menu

NeoAI / Security

Your cloud, your data, your recipes.

NeoAI is designed to run in your own VPC, behind your existing AI gateway. Prompts never train anything for other customers, you own the recipes and can export them, and every recipe version is logged and auditable. A data processing agreement is available; SOC 2 and ISO 27001 status is still to be confirmed.

Last updated 25 Oct 2026 · By NeoAI

Scroll

NeoAI runs inside your cloud boundary.

Commitment

NeoAI, the recipe store, the evaluation harness and the audit log all run inside your cloud boundary, behind your existing AI gateway.

What we commit to, and what is still to be confirmed.

Commitment means a design commitment your security team can verify in the audit and pilot. Nothing here claims a certification NeoAI does not yet hold.
AreaWhat NeoAI commits toStatus
DeploymentRuns in your VPC, behind your AI gatewayCommitment
Data usePrompts never train anything for other customersCommitment
RecipesOwned by you and exportableCommitment
AuditabilityEvery recipe version loggedCommitment
ReliabilityA failed step escalates; no user-facing errorCommitment
Data processing agreementAvailable SOC 2To be confirmed ISO 27001To be confirmed
Audit log · Resume screeningSample data
# v14 vs v13, step 3
+ check: every_score_cites_evidence
  evidence: accepted runs, sample data

Every recipe version is logged and auditable.

Who or what changed it, when, and the evidence behind it. Select a version to see the change.

Illustration of the log layout, not customer data. Illustrative

You own the recipes, and you can take them with you.

  1. Owned by you. Built from your own work.
  2. Exportable. A plain file, not a black box.
  3. Versioned. Every version logged.
resume-screening-v14.yamlIllustrative
recipe: resume-screening
version: 14
owner: your-company
steps:
  - job_description_to_rubric
  - score_evidence
  - calibrate_and_bias_check
  - shortlist_note
context: [role_brief, scoring_rubric, last_3_accepted_shortlists]
tools: [cv_parser, ats_lookup]
checks: [every_score_cites_evidence, no_protected_attributes]

Example file layout, for illustration. Illustrative

Quality is tested on your prompts before go-live.

1Your evaluation setreal tasks→ 2Your acceptance criteriayour bar→ 3Pass the barmethod open to your team→ 4Go-liveone endpoint change
After go-live: a step that fails a confidence or quality check escalates to a higher tier automatically (Small → Mid). The user gets a result, never an error.

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 plan and status are still to be confirmed. We will say so plainly in any security review.

Start a review: contact@neoai.solutions or request the free audit.

Questions buyers ask before they book.

Where does NeoAI run?

In your own VPC, behind your existing AI gateway. The recipe store, evaluation harness and audit log are inside your cloud boundary.

Does NeoAI train models on our prompts?

No. Prompts never train anything for other customers.

Who owns the recipes NeoAI learns?

You do. Recipes are owned by you and exportable, and every version is logged and auditable.

Is NeoAI SOC 2 or ISO 27001 certified?

Certification status is still to be confirmed. A data processing agreement is available.

Prefer to read it? The full page is here.

Every table, definition and source from this page, as plain text.

Read the full page

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

Status labels: Commitment means a design commitment that your security team can verify in the audit and pilot. Nothing here claims a certification NeoAI does not yet hold.
AreaWhat NeoAI commits toStatus
DeploymentRuns in your VPC, behind your existing AI gatewayCommitment
Data usePrompts never train anything for other customersCommitment
Recipe ownershipRecipes are owned by you and exportableCommitment
AuditabilityEvery recipe version is logged and auditableCommitment
ReliabilityAutomatic fallback: a failed step escalates, and the user never sees an errorCommitment
Data processing agreementDPA availableAvailable
SOC 2 / ISO 27001Certification plan to be shared with your security teamTo 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.