BasekickLabs

Arc Enterprise

Arc Enterprise adds clustering, RBAC, tiered storage, audit logging, and query governance to the Arc binary. Enable them with a license key in arc.toml; no data migration.

Production-grade time-series database infrastructure for scale, security, and compliance.

Arc Enterprise extends the Arc time-series database with enterprise features designed for production deployments. Same binary, same performance — with clustering, access control, tiered storage, audit logging, and more.

Arc Enterprise Architecture

OSS vs Enterprise

CapabilityArc OSSArc Enterprise
Deployment & Scale
Single-node deploymentYesYes
Clustering (multi-node)-Yes
Role separation (writer / reader / compactor)-Yes
Automatic failover (writer + compactor)-Yes
Shared-storage deployment (S3 / MinIO / Azure)YesYes
Local-storage deployment with peer replication-Yes
Heartbeat-based cluster health detection-Yes
Security & Access
Token-based authenticationYesYes
Organizations, teams, and RBAC-Yes
Measurement-level permissions-Yes
Cluster TLS encryption + shared secret auth-Yes
Audit logging-Yes
Data Lifecycle
Continuous queries (manual execution)YesYes
Retention policies (manual execution)YesYes
Automatic scheduling (continuous queries + retention policies)-Yes
Auto-aggregation-Yes
Hot/cold tiered storage with per-database policies-Yes
Backup & restore-Yes
Observability & Operations
Prometheus metricsYesYes
Active query management-Yes
Query governance (rate limits, quotas, row limits)-Yes
SLA monitoring-Yes
Integrations
MQTT subscription managementYesYes
Storage
S3 / Azure / MinIO storageYesYes

Getting started

Arc Enterprise uses the same binary as Arc OSS. Enable enterprise features by adding your license key:

# arc.toml
[license]
key = "ARC-XXXX-XXXX-XXXX-XXXX"

Or via environment variable:

export ARC_LICENSE_KEY="ARC-XXXX-XXXX-XXXX-XXXX"

On startup, Arc validates your license and enables the features included in your plan. No data migration is required — your existing databases, measurements, and configurations are fully preserved.

Once the node is running, follow the shared Writing data guide for MessagePack and line protocol examples in curl, Python, and Go.

Zero-Downtime Upgrade

Upgrading from Arc OSS to Enterprise requires no data migration. Add your license key, enable the features you need, and restart. Your existing data and configuration remain intact.

Features

Configuration example

A complete enterprise configuration combining multiple features:

# arc.toml — Enterprise deployment example

[license]
key = "ARC-XXXX-XXXX-XXXX-XXXX"

[server]
port = 8000

[storage]
backend = "s3"
s3_bucket = "arc-production"
s3_region = "us-east-1"

[auth]
enabled = true

[cluster]
enabled = true
node_id = "writer-01"
role = "writer"
cluster_name = "production"
seeds = ["10.0.1.10:9000", "10.0.1.11:9000"]

[tiered_storage]
enabled = true
default_hot_max_age_days = 30

[tiered_storage.cold]
enabled = true
backend = "s3"
s3_bucket = "arc-archive"
s3_region = "us-east-1"

[audit_log]
enabled = true
retention_days = 90

[governance]
enabled = true
default_rate_limit_per_min = 60
default_max_queries_per_hour = 500

[query_management]
enabled = true

Get a license

Tiers, activation limits, renewals, and expiry are covered in Licensing.

On this page