Blog

Engineering
We Forked Our Serialization Library. It Was 21% Slower Than It Needed to Be.
Arc serializes millions of records per second. When we profiled the hot path, msgpack was allocating memory on every single call. So we forked it, rewrote the internals, fixed 15 bugs the upstream had ignored for years, and shipped v6.0.0. Here's the full story.

Product
We Got It Wrong: Why Arc Isn't a Time-Series Database

Product
Arc 26.03.1: Backup & Restore, TLE Ingestion, and 13 Bugs That Won't Bother You Anymore

Product
Why Aerospace Companies Are Choosing Arc for Satellite Telemetry

Product
Arc 26.02.2: Bulk Import, Query Governance, and the WAL Fix That Saved Your Data

Product
13 Years of NYC Citibike Data. 153 Million Trips. One Arc Instance.

Engineering
I Let an AI Agent Run My Social Media for 3 Days. Arc Remembered Everything.

Product
Arc Enterprise: When Your Single Node Isn't Enough Anymore

Product
Arc 26.02.1: MQTT, InfluxDB Drop-In Compatibility, and 480 Servers Later

Engineering
We Benchmarked Arc Against Every Major Log Database. The Results Were Brutal.

Tutorials
How to Secure Your Time-Series Database with Traefik and Let's Encrypt

Liftbridge
Liftbridge 26.01.1: CalVer, Reverse Subscriptions, and 241K msgs/sec

Engineering
Getting Started with the Python SDK for Arc
Ready to handle billion-record workloads?
Deploy Arc in minutes. Own your data in Parquet. Use for analytics, observability, AI, IoT, or data warehousing.
