Aleria is sovereign by design. It runs inside your own boundary, your data never leaves it, and your information is never used to train shared models. This is the core promise of the product, not a setting you have to find. The product experience is the same wherever it runs; what changes is where the work happens.
Your data never leaves your boundary. Aleria makes no external API calls with your content, and your information is never used to train shared models — this holds in Private Cloud, on-premises, and fully air-gapped deployments.
The two access options
Aleria is delivered in one of two ways. Both keep your data inside your boundary.
Aleria Private Cloud
Aleria hosts and operates the platform for you, in an environment that is private and isolated to your organization, in a region you choose for data residency. This is the fastest way to get started, and it still keeps your data separated from anyone else's. It fits teams that want a managed service without sharing infrastructure.
On-premises
Aleria is installed in your own data center, so data never leaves your infrastructure at all. This fits regulated industries, government, and organizations that must keep everything inside their own walls. On-premises also supports a fully air-gapped install, with no internet connection, for the highest-sensitivity environments such as classified networks and certain defense and critical-infrastructure programs.
Which one fits you
The choice is simple:
- If you can run Aleria as a managed but private service, Aleria Private Cloud is the quickest path.
- If your rules require everything to stay inside your own data center, choose on-premises.
- If your environment cannot have any internet connection, choose the air-gapped on-premises install.
You can start with one and move to the other as your requirements change.
Why your data stays put
Because Aleria runs its own models inside your boundary, it does not call out to third-party AI services. Your prompts, files, and results stay where you are. This is also why the model catalog is made up of Aleria's own models and selected open models rather than outside services. See Choose a model.
Security
The exact controls available depend on which option you run and how it is configured, so confirm the specifics with your account team. The following are part of how Aleria protects access and data.
Sign-in and identity
- Single sign-on with Google, Microsoft, and Apple accounts.
- Passkeys for strong, phishing-resistant sign-in.
- Aleria can also act as an identity provider for the apps you build, using standard OpenID Connect.
- If your organization uses a specific enterprise identity system, ask your account team what is supported for your deployment.
Access control
- Role-based access at the organization and workspace level (Owner, Admin, Member). See Workspaces.
- Per-member permissions for sensitive actions, such as who can invite people or create workflows.
- Row-level and column-level data rules carried through from your connected sources, so people only see what they are allowed to see. See Big Data Fusion.
Encryption and connections
- Traffic is encrypted in transit using current TLS standards.
- Encryption at rest and key-management options are available and depend on your deployment.
- Passwords, where used, are stored using strong, modern hashing.
Monitoring
- Aleria exports operational metrics and traces using OpenTelemetry, so it fits your existing monitoring stack.
- Detailed activity logging and the ability to forward logs to your own security tools depend on your deployment. Your account team can describe what is available.
Data handling
- No training on your data. Your data is used only to answer your questions. It is never mixed into shared model training. This is a hard product rule.
- Your data stays in your boundary. Nothing is sent to an outside AI provider.
- Retention you control. How long chats, files, and generated artifacts are kept can be configured for your organization.
- Deletion. Data removal is handled according to your agreement with Aleria.
Compliance
Aleria is built to fit regulated environments. Certifications and regulatory alignments vary by region and deployment and change over time, so for your current compliance package and any specific certifications, talk to your account team.
Getting started
Many organizations begin with a single department, prove the value, and expand from there. You do not have to choose the most locked-down option on day one. Aleria is designed so your data and configuration can move as your requirements change. For help choosing, talk to your account team.
Common questions
What are the two ways I can deploy Aleria?
There are two options. With Aleria Private Cloud, Aleria hosts and operates the platform in an environment that is private and isolated to your organization, in a region you choose. Or you can run Aleria on-premises in your own data center, which can also run fully air-gapped with no internet connection.
Does my data ever leave my boundary?
No. Aleria runs its own models inside your boundary, so your prompts, files, and results stay where you are and nothing is sent to an outside AI provider.
Is my data used to train shared models?
No. Your data is used only to answer your questions and is never mixed into shared model training. This is a hard product rule.
What sign-in and identity options are available?
You can sign in with single sign-on using Google, Microsoft, and Apple accounts, or with passkeys for phishing-resistant sign-in. Aleria can also act as an OpenID Connect identity provider for the apps you build. If your organization uses a specific enterprise identity system, ask your account team what is supported for your deployment.
Where can I confirm specific certifications for my deployment?
Certifications and regulatory alignments vary by region and deployment and change over time. For your current compliance package and any specific certifications, talk to your account team.