Deployment

A practical path from one workflow to an operating layer.

Choose the deployment path, governance depth, and operating scope that match your enterprise environment and ambition.

Cloud

Private

Hybrid available

Pilot

For one high-value workflow with clear outputs and human review.

​1

workflow

What’s included

Approved context setup

Workflow configuration

Human approval gate

Audit-ready run logs

Expansion plan

Scale

Popular

For multiple teams standardizing reusable agent workflows on one governed platform.

​2

teams

What’s included

Multiple workflows

Reusable workflow packs

SSO and role controls

Model routing

Production observability

Production observability

Enterprise

For company-wide agent operations with private infrastructure and advanced governance.

​1

company-wide platform

What’s included

Private or hybrid deployment

Local model support

Granular ACE permissions

Controlled write-back

Dedicated support

Dedicated support

Cloud

Private

Hybrid available

Pilot

For one high-value workflow with clear outputs and human review.

​1

workflow

What’s included

Approved context setup

Workflow configuration

Human approval gate

Audit-ready run logs

Expansion plan

Scale

Popular

For multiple teams standardizing reusable agent workflows on one governed platform.

​2

teams

What’s included

Multiple workflows

Reusable workflow packs

SSO and role controls

Model routing

Production observability

Production observability

Enterprise

For company-wide agent operations with private infrastructure and advanced governance.

​1

company-wide platform

What’s included

Private or hybrid deployment

Local model support

Granular ACE permissions

Controlled write-back

Dedicated support

Dedicated support

Cloud

Private

Hybrid available

Pilot

For one high-value workflow with clear outputs and human review.

​1

workflow

What’s included

Approved context setup

Workflow configuration

Human approval gate

Audit-ready run logs

Expansion plan

Scale

Popular

For multiple teams standardizing reusable agent workflows on one governed platform.

​2

teams

What’s included

Multiple workflows

Reusable workflow packs

SSO and role controls

Model routing

Production observability

Production observability

Enterprise

For company-wide agent operations with private infrastructure and advanced governance.

​1

company-wide platform

What’s included

Private or hybrid deployment

Local model support

Granular ACE permissions

Controlled write-back

Dedicated support

Dedicated support

Compare the operating scope behind each deployment program.

Enterprise

1

company-wide platform

Platform foundation

Workbench access

Included

Included

Included

Library context

Selected scope

Multiple domains

Enterprise-wide

Studio workflows

One workflow

Multiple workflows

Portfolio scale

Admin control

Governance

File and folder permissions

Included

Included

Included

Human approval gates

Enterprise SSO

Audit and observability

Controlled write-back

Selected actions

Multiple systems

Policy-based

Cloud deployment

Deployment

Azure deployment

Optional

Available

Available

On-premises or hybrid

Local model support

Support

Workflow design

Reusable packs

Solution architecture

Partner-led delivery

Available

Enterprise

1

company-wide platform

Platform foundation

Workbench access

Included

Included

Included

Library context

Selected scope

Multiple domains

Enterprise-wide

Studio workflows

One workflow

Multiple workflows

Portfolio scale

Admin control

Governance

File and folder permissions

Included

Included

Included

Human approval gates

Enterprise SSO

Audit and observability

Controlled write-back

Selected actions

Multiple systems

Policy-based

Cloud deployment

Deployment

Azure deployment

Optional

Available

Available

On-premises or hybrid

Local model support

Support

Workflow design

Reusable packs

Solution architecture

Partner-led delivery

Available

Pilot

Scale

Enterprise

Platform foundation

Workbench access

Included

Library context

Selected scope

Studio workflows

One workflow

Admin control

Governance

File and folder permissions

Included

Human approval gates

Enterprise SSO

Audit and observability

Controlled write-back

Selected actions

Cloud deployment

Deployment

Azure deployment

Optional

On-premises or hybrid

Local model support

Support

Workflow design

Reusable packs

Solution architecture

Partner-led delivery

Frequently asked questions.

Learn how BasilAOS connects enterprise context, governed execution, deployment, and approved learning. Still evaluating? Talk to contact@basilos.ai.

General

Getting Started

Platform

Integrations

Security and Governance

Where should an enterprise begin?

Begin with one frequent, context-heavy workflow that has a concrete output, an identifiable owner, an existing review point, and a measurable baseline. The first deployment should also create connectors, permissions, templates, and evaluation assets the next workflow can reuse.

What makes a good first workflow?

A good first workflow is valuable enough to matter and bounded enough to govern. It usually crosses several sources, produces a report, diagnosis, proposal, record, or approved action, and has clear measures such as turnaround time, effort, error rate, or service capacity.

How much data preparation is required?

It depends on the workflow. BasilAOS can begin with selected folders, records, systems, and business rules rather than a company-wide data migration. The important work is defining authoritative sources, permissions, metadata, and the context needed for the chosen outcome.

Can BasilAOS work with cloud and local models?

Yes. Admin can manage model groups across cloud APIs and local serving. Enterprises can route tasks to approved models based on capability, sensitivity, cost, latency, or infrastructure requirements.

Can employees use local files?

Yes. BasilAOS supports in-chat uploads and encrypted two-way synchronization between selected local folders and approved agent cloud resources, with scope, read-only state, and agent permissions visible.

Can agents write back to business systems?

Yes, when the connector and workflow are configured for it. Write-back should be limited by identity, permissions, validation, policy, approval gates, and audit rather than enabled as an unrestricted agent capability.

Frequently asked questions.

Learn how BasilAOS connects enterprise context, governed execution, deployment, and approved learning. Still evaluating? Talk to contact@basilos.ai.

General

Getting Started

Platform

Integrations

Security and Governance

Where should an enterprise begin?

Begin with one frequent, context-heavy workflow that has a concrete output, an identifiable owner, an existing review point, and a measurable baseline. The first deployment should also create connectors, permissions, templates, and evaluation assets the next workflow can reuse.

What makes a good first workflow?

A good first workflow is valuable enough to matter and bounded enough to govern. It usually crosses several sources, produces a report, diagnosis, proposal, record, or approved action, and has clear measures such as turnaround time, effort, error rate, or service capacity.

How much data preparation is required?

It depends on the workflow. BasilAOS can begin with selected folders, records, systems, and business rules rather than a company-wide data migration. The important work is defining authoritative sources, permissions, metadata, and the context needed for the chosen outcome.

Can BasilAOS work with cloud and local models?

Yes. Admin can manage model groups across cloud APIs and local serving. Enterprises can route tasks to approved models based on capability, sensitivity, cost, latency, or infrastructure requirements.

Can employees use local files?

Yes. BasilAOS supports in-chat uploads and encrypted two-way synchronization between selected local folders and approved agent cloud resources, with scope, read-only state, and agent permissions visible.

Can agents write back to business systems?

Yes, when the connector and workflow are configured for it. Write-back should be limited by identity, permissions, validation, policy, approval gates, and audit rather than enabled as an unrestricted agent capability.

Frequently asked questions.

Learn how BasilAOS connects enterprise context, governed execution, deployment, and approved learning. Still evaluating? Talk to contact@basilos.ai.

Where should an enterprise begin?

Begin with one frequent, context-heavy workflow that has a concrete output, an identifiable owner, an existing review point, and a measurable baseline. The first deployment should also create connectors, permissions, templates, and evaluation assets the next workflow can reuse.

What makes a good first workflow?

A good first workflow is valuable enough to matter and bounded enough to govern. It usually crosses several sources, produces a report, diagnosis, proposal, record, or approved action, and has clear measures such as turnaround time, effort, error rate, or service capacity.

How much data preparation is required?

It depends on the workflow. BasilAOS can begin with selected folders, records, systems, and business rules rather than a company-wide data migration. The important work is defining authoritative sources, permissions, metadata, and the context needed for the chosen outcome.

Can BasilAOS work with cloud and local models?

Yes. Admin can manage model groups across cloud APIs and local serving. Enterprises can route tasks to approved models based on capability, sensitivity, cost, latency, or infrastructure requirements.

Can employees use local files?

Yes. BasilAOS supports in-chat uploads and encrypted two-way synchronization between selected local folders and approved agent cloud resources, with scope, read-only state, and agent permissions visible.

Can agents write back to business systems?

Yes, when the connector and workflow are configured for it. Write-back should be limited by identity, permissions, validation, policy, approval gates, and audit rather than enabled as an unrestricted agent capability.

Move enterprise AI from pilots into production.

Move enterprise AI from pilots into production.

Move enterprise AI from pilots into production.