Skip to content
AI
Menu

Your documents, your instance, your decisions

Aerya AI handles certificates, drawings and supplier documents that belong to you and your customers. These are the rules it is built on, today.

One instance per customer

  • Each customer gets a separate installation: its own database, file storage, secrets and address.
  • No shared tables and no row-level separation that a bug could break.
  • Your documents stay in your instance's file storage.

AI calls

  • Every model call goes through one gateway with zero data retention set on the request itself.
  • Customer documents are only sent through the EU endpoint.
  • Claude models run on Amazon Bedrock or Google Vertex, providers that do not store your documents or train on them.
  • Every call is logged with model, provider, tokens, cost and a hash of the document.

People decide

  • Nothing is written to your ERP without a person's approval.
  • Pass or fail is decided by code against your spec tables, never by the model.
  • Every write lands in an append-only audit log: who approved what, and when.

Access

  • Roles for admins, quality, purchasing and viewers.
  • Two-factor sign-in is required for administrators.
  • ERP credentials are encrypted at rest with a key kept outside the database.
  • Webhooks from your ERP are signed and rejected outside a short time window.

On the roadmap

For larger companies and their IT security reviews, these come next:

  • Single sign-on with Microsoft Entra ID
  • Data processing agreement and a security pack: architecture, data flows, subprocessors
  • External penetration test
  • ISO 27001
  • Installation in your own cloud, with the same images

Which check does your team still do by hand?

Tell us about it. We show you Aerya AI on synthetic documents of the same kind, and tell you honestly whether it fits.