Deployment
Cloud, enterprise or hybrid.
Run AVELIN in our cloud, on your own GPUs, or both. You choose where the models run and what can leave. The Decision Layer picks the right model for every request in all three.
Pick where AVELIN runs
Three deployments. Choose by where your data must be processed.
AVELIN Cloud
Best for teams that want to start now and cut token spend.
- Nine AVELIN models and the Decision Layer behind one API
- Connect your own AI providers
- Zero retention by default
Enterprise
Best for teams whose data must be processed on their own GPUs.
- The Decision Layer, the full platform, or both
- Inference optimized for your GPUs
- Models tuned to your workflows
Hybrid
Best for teams that want local control and extra intelligence on demand.
- Local models on your GPUs
- Offload to a public model when needed
- A privacy check applies your rule
AVELIN Cloud
Use the AVELIN models and the Decision Layer through one API. Switch by changing the base URL and the API key.
The Decision Layer.
It reads each request and picks the model it needs. Hard tasks go to a capable model. Easy tasks go to a cheaper one.
Your own providers.
Connect the AI providers you already use. The Decision Layer helps you cut token spend across them.
Global inference.
Requests are served from the United States, Europe and MENA. Isolated in-country locations are planned.
Zero retention by default.
We do not keep your prompts or answers, and they are not used to improve AVELIN unless you opt in. The data policy has the detail.
Enterprise
AVELIN on GPUs you control. Use the Decision Layer on your workflows, the full platform, or both.
The Decision Layer on your workflows.
Put it in front of your apps and agents. It picks the right model for every request, from the models you allow.
The full platform on your GPUs.
The AVELIN inference layer, the nine models and the API platform, installed on your hardware and optimized for your GPUs.
Tuned to your workflows.
Models can be fine-tuned or trained on your own workflows, so they fit your tasks.
Your data, your network.
Prompts are processed on your GPUs, which is the ultimate privacy. The written scope lists every network path the software opens.
Hybrid
Local models run on your GPUs. When a task needs more intelligence, or your local model is busy, AVELIN can send it to a public model. A privacy check lets you decide whether detected private data may leave.
The privacy check, step by step
Read.
The Decision Layer reads each request and picks a model. Your local model is the default.
Decide.
If the task needs more intelligence, or your local model is under heavy load, a public model becomes an option.
Check.
Before anything leaves your GPUs, the privacy check looks for private data in the request.
Apply your rule.
You decide. Detected private data may go to a public model, or it must stay on your GPUs.
Send.
The request stays on your GPUs, or goes to a public model. Every offloaded request passes the check first.
Where models run and where data goes
The same questions, answered three ways.
| Question | AVELIN Cloud | Enterprise | Hybrid |
|---|---|---|---|
| Where the models run | AVELIN infrastructure | Your GPUs | Local models on your GPUs. Public models when you allow it. |
| Where requests are processed | The United States, Europe and MENA | On your GPUs, in your network | On your GPUs by default. At a public model after an offload. |
| What AVELIN keeps | Zero retention by default | Set in the written scope | Set in the written scope |
| Can a request leave? | It is served by AVELIN and the providers you connect | You decide. The scope lists every network path. | Only through the privacy check, by your rule |
In-country locations
We are planning isolated locations inside a single country or region, so your data does not cross a border.
If your data must stay in one country or region, say so in your POC request. The scope states where your data is processed before any data is sent.
Questions about deployment
Which deployment fits us?
Choose AVELIN Cloud to start now and cut token spend. Choose enterprise if your data must be processed on your own GPUs. Choose hybrid if you want local models, extra intelligence from public models when needed, and your own rule for private data.
What is hybrid?
Hybrid runs local models on your GPUs. It can offload a request to a public model when a task needs more intelligence or your local model is under heavy load. A privacy check applies your rule first.
What does the privacy check do?
It looks for private data in a request before the request can leave your GPUs. You decide what happens: detected private data may go to a public model, or it must stay on your GPUs.
When does a request go to a public model?
When the task needs more intelligence than your local model offers, or when your local model is under heavy load. It goes only if the privacy check allows it under your rule.
Where does cloud inference run?
Requests are served from the United States, Europe and MENA. The data policy lists the exact countries. If your data must stay in one country or region, say so in your POC request.
What are isolated in-country locations?
They are locations in a single country or region where your data does not cross a border. They are planned for AVELIN Cloud.
What is a sovereign AI platform deployment?
It is a deployment where you, not a vendor or a cloud, decide where the system runs and who can reach it. An AVELIN enterprise deployment is one.
How do we start?
Request a POC on one of your workloads. The scope states where your data is processed before any data is sent.
Choose where it runs. Prove it first.
A POC is a proof of concept on your own workload. Tell us which deployment you are weighing and we scope it with you.