Deployment models

Your deployment model decides who operates Fluso and where its runtime, durable data, and diagnostics can live. It does not by itself control where connected Apps or external model providers process data.

Model	Availability	Operations
Fluso Cloud	Available	Managed by Fluso
Fluso Local	Contact Fluso for a matching Mac or Linux package	You operate one owner's workspace
Dedicated AWS VPC	Supported for scoped Enterprise deployments	Responsibilities agreed during deployment design
Azure VNet	Coming soon	Not available today
On-premises	Scoped Enterprise engagement	Responsibilities agreed before implementation

Fluso Cloud

Fluso Cloud is the standard managed service. It runs on AWS with European hosting by default. Fluso operates the application services, Agent runtimes, storage, and platform updates; you manage your workspace, users, connected Apps, and approval policies.

Choose it when you want to start without operating infrastructure. See Legal for Fluso's privacy policy.

Fluso Local

Install the daemon to run one owner's workspace on an Apple Silicon Mac or a supported Linux host. Conversations and files stay on that host. You manage its provider credentials, service, updates, and backups.

The desktop app connects to this workspace. It does not install or update the daemon. This is separate from an Enterprise deployment of the whole platform. Start with Set up Fluso Local.

Dedicated AWS VPC

A dedicated AWS VPC deployment is available for Enterprise customers whose network or residency requirements do not fit the managed service. It is a scoped deployment, not a self-service switch.

Before launch, your team and Fluso agree on AWS account ownership, region, network connectivity, ingress and egress, DNS, secrets, data stores, backups, upgrades, and support access.

Azure VNet (coming soon)

Azure VNet support is planned but is not available today. There is no published availability date. Do not make an Azure deployment dependency until Fluso confirms the required region and services are supported.

On-premises

On-premises deployments are scoped with Enterprise customers against the target infrastructure. Fluso does not currently offer a one-click installer or a generic support promise for every Kubernetes, virtual-machine, or bare-metal environment.

Agree on these boundaries before treating the design as approved:

Boundary	What to decide
Data residency	Where the database, project files, knowledge data, and backups are stored
Runtime and inference residency	Where Agent runtimes execute and which model endpoints may receive requests
Diagnostic-data residency	What diagnostic data is captured, where it is stored, how long it is retained, and who can access it
Network access	Which inbound paths and outbound destinations are permitted
Connected Apps	Which external systems may be read or changed, and what returned data Fluso may persist

Running Fluso on-premises does not automatically keep model inference or connected-App data on-premises. External providers keep their own processing boundaries. Confirm every provider and route as part of the deployment design. See Legal for Fluso's privacy policy.

Operational telemetry

AWS deployments send service logs to CloudWatch and define CloudWatch alarms. Fluso's knowledge service emits structured logs and can export traces and metrics through OpenTelemetry (OTLP). The current AWS collector routes traces to X-Ray and metrics to CloudWatch; Prometheus scraping is optional.

Traces can include prompt and response text. For a dedicated or on-premises deployment, agree which signals are captured, where they are stored, how long they are retained, and which customer-owned collectors are supported.

Choose a model

Start with Fluso Cloud when managed operations and European hosting meet the requirement.
Use Fluso Local when you want to operate a workspace on your own machine.
Scope an AWS VPC deployment when you need a dedicated AWS network boundary.
Treat Azure VNet as future availability, not a current option.
Scope on-premises only after Fluso validates the infrastructure, residency, provider, telemetry, and support requirements.

For a custom deployment, contact Fluso.