Pricing and deployment options

Choose where DataKnobs runs.
Keep the intelligence consistent.

DataKnobs supports two deployment models. Large enterprises can deploy DataKnobs and EKIP inside their own cloud, data, and AI infrastructure. Small and mid-sized organizations can use DataKnobs-managed infrastructure for a faster, turnkey path to production.

Compare deployment options Help me choose

Same DataKnobs capabilities Different operating model Portable by design

Two deployment models

Use your infrastructure—or use ours.

The platform capabilities stay consistent. The difference is who owns and operates the cloud, data platform, model endpoints, and production environment.

Enterprise default

Customer-owned infrastructure

DataKnobs and EKIP are deployed into the customer's approved cloud, data platform, model environment, and security boundary.

Best fit

Large enterprises, regulated businesses, companies with confidential data, complex integrations, existing cloud discounts, or mature platform operations.

Customer controls cloud, LLM, storage, and networking contracts
Data stays within the customer's environment and governance boundary
Supports private networking, enterprise IAM, SSO, audit, and security controls
Works with Snowflake, Databricks, BigQuery, AWS, Azure, Google Cloud, and private cloud
DataKnobs provides the intelligence, governance, evaluation, and optimization layer

View customer-owned infrastructure pricing

Recommended when data sensitivity, enterprise integration, or scale is the primary concern.

Turnkey managed option

DataKnobs-managed infrastructure

DataKnobs hosts and operates the required environment, while customers receive transparent metering, controls, and prepaid usage budgets.

Best fit

Small and mid-sized companies, teams without dedicated cloud operations, pilots, new Data Products, and workloads using public or non-confidential data.

DataKnobs manages hosting, monitoring, backups, operations, and environment maintenance
Faster setup with fewer internal infrastructure dependencies
Prepaid cloud and LLM consumption budgets
Usage alerts, approval gates, cost forecasts, and hard stops
Portability can be built in so the deployment can move later

View managed infrastructure pricing

Recommended when speed, simplicity, and lower operational overhead matter most.

How to choose

Three questions usually determine the right model.

How sensitive is the data?

Confidential, regulated, proprietary, customer, employee, financial, or health-related data generally favors customer-owned infrastructure.

How mature are your operations?

Organizations with established cloud, security, data engineering, and procurement teams usually benefit from deploying DataKnobs inside their existing environment.

How quickly do you need to launch?

Companies seeking a simpler and faster path—especially for public or low-sensitivity data—can start with DataKnobs-managed infrastructure.

Data sensitivity matters

Public and non-confidential data is easier to run on DataKnobs infrastructure.

The deployment decision is not only about company size. Data classification, contractual obligations, and integration complexity may be more important.

Good fit for managed infrastructure

Public or low-sensitivity data

These workloads are often easier to operate on DataKnobs-managed infrastructure:

Public market, regulatory, legal, government, or open-data sources
Public websites, product catalogs, location pages, or published documents
Non-confidential research, benchmarking, evaluation, and experimentation
Pilots where confidential enterprise data is not required

Usually better in customer infrastructure

Confidential or regulated data

These workloads generally favor customer-owned infrastructure:

Customer records, employee information, financial data, or internal documents
Regulated information subject to privacy, banking, healthcare, or contractual controls
Proprietary models, source data, trade secrets, or sensitive business workflows
Deep integrations with internal warehouses, operational systems, and security controls

Side-by-side comparison

One platform. Two operating models.

Consideration	Customer-owned infrastructure	DataKnobs-managed infrastructure
Typical customer	Large enterprise or regulated organization	Small or mid-sized company, business unit, pilot, or focused team
Data sensitivity	Best for confidential and regulated data	Best for public or non-confidential data
Cloud and LLM contracts	Owned directly by customer	Managed by DataKnobs within an approved budget
Environment operations	Customer or its managed provider	DataKnobs
Deployment speed	Depends on enterprise onboarding and security review	Usually faster
Integration depth	Best for complex enterprise systems	Best for standard or lighter-weight integrations
Cost control	Customer manages provider bills directly	Prepaid budgets, alerts, approval gates, and hard stops
Portability	Native to customer environment	Can be designed for later migration
Recommended default	Enterprise default	Qualified based on data, workload, and usage profile

Start managed, then move—or begin directly in your environment.

The deployment model does not need to be permanent. A company can start with DataKnobs-managed infrastructure for a pilot or public-data use case, then migrate to customer-owned infrastructure as sensitivity, scale, or integration requirements increase.

Explore managed pricing Explore customer-owned pricing

FAQ

Common deployment questions.

Do both deployment options include the same DataKnobs capabilities?

Yes. Both models can include Data Products, Knobs, governance, lineage, evaluation, monitoring, experimentation, optimization, and EKIP capabilities. The main difference is who owns and operates the infrastructure.

Should every large company use customer-owned infrastructure?

Not necessarily. Large companies may still use DataKnobs-managed infrastructure for public-data workloads, isolated pilots, demonstrations, or use cases that do not require access to confidential systems.

Can a small company still use its own infrastructure?

Yes. Company size is only one factor. A smaller company may prefer customer-owned infrastructure when it has sensitive data, strict contractual obligations, or established cloud operations.

Can we move from managed infrastructure to our own cloud later?

Yes. Portability should be designed into the architecture, deployment process, and agreement. Migration services may be separately scoped.

Which model is best for public data products?

DataKnobs-managed infrastructure is often the simplest option for public market data, public legal and regulatory data, public websites, catalogs, published documents, and other non-confidential sources.

Choose the infrastructure model that matches your data, scale, and operating maturity.

DataKnobs can help classify the workload, estimate consumption, identify security requirements, and recommend the right deployment path.

Request a deployment assessment