Enterprise

The whole engine, on your terms.

Run Auld on the managed service, keep the memory store in your own cloud account, or deploy the full engine there. Add SSO, larger recall budgets and custom retrieval.

Deployment models

Three ways to run it.

ManagedYour databaseFull deployment
Engine runsManaged infrastructureManaged infrastructureYour cloud account
Memory storedManaged infrastructureYour cloud accountYour cloud account
Who operatesAuldAuld operates the engine; you own the storeOperated under agreement in your account
NetworkPublic API endpointEngine connects to your store over a private link you approveInside your network boundary
PlansPay as you go, Flex, EnterpriseEnterpriseEnterprise
Clouds—AWS, Google Cloud, AzureAWS, Google Cloud, Azure
Architectureown-cloud options
Enterprise deployment architectureYour applications call the Auld engine. In the database-only model the engine is managed and storage sits in your cloud account; in the full model both sit inside your account. YOUR CLOUD ACCOUNT (AWS · GOOGLE CLOUD · AZURE) YOUR APPS & AGENTSREST · MCP · webhooks AULD ENGINEextraction · reconcilerecall · access controlfull deployment MEMORY STORErecords · memoriesyour keys & backupsboth models Database-only model: the engine runs on managed infrastructure and connects to the store in your account.

Capabilities

What Enterprise adds.

  • ScaleFrom 5,000,000 credits a monthUnlimited recall, unlimited projects, 1,000 requests per minute.
  • ContextUp to 32,000 tokens per recallLarger evidence pages for complex reviews and long cases.
  • IdentitySSO and SAMLConsole access through your identity provider.
  • RetrievalCustom retrieval configurationEntity types, edges and ranking tuned to your domain.
  • RetentionUnlimited storage and retentionIncluding unlimited API log retention.
  • SupportSlack or Teams with an account managerA named contact for rollout and reviews.

Governance

Governed at the data layer.

Access control lives with the data: every memory carries the visibility of the records it came from, so the same rule holds in every client — REST, MCP or plugins.

  • Per-record visibility: project, audience or single user.
  • Deletion by record, identity or project, including derived memories.
  • Request logs for every call, with identity and key.
  • Keys scoped by type: secret, recall-only, MCP.

Talk to us

Tell us about your deployment.

Share your cloud, data residency, identity provider and expected volume. We will reply by email to arrange a call.

Records or bytes per month, if known.

Residency, identity provider, review process, timeline.

Nothing is sent from this page. Submitting prepares an email to support@auld.app that you review and send from your own email app.