Founder & engineer · Basekick Labs
Twenty years in and around technical teams taught me the same lesson over and over: the valuable thing is easy to hand over and expensive to get back. So I build the opposite. Arc keeps telemetry history in open Parquet on storage you control. Basekick Git keeps your repositories and runners inside your own boundary. Both at Basekick Labs, and I'm writing about it as it happens.
The flagship · Creator & maintainer
Most time-series databases make you choose between keeping your history and affording it. Arc doesn't. It ingests through InfluxDB Line Protocol, writes standard Apache Parquet to storage you own, and queries recent and historical data through one SQL surface, with no retention cliffs, no proprietary formats, and no separate cold-data stack. One Go binary, DuckDB as the query engine, and the whole pipeline around it: ingestion, compaction, retention policies, continuous queries, auth, backup and restore.
Building now · Founder
Code review is a collaboration problem. Where the repositories live is an infrastructure decision. Bundling the two is why changing a code host turns into a migration. Basekick Git separates them: pull requests, inline review, branch protection, and CI coordination sit on top, while repository objects and runners stay in storage and on machines you control. Plain Git underneath, so there is nothing proprietary to unwind. Revoke our access and you still have a standard repository and your collaboration data.
The company · Founder
Infrastructure teams own, for the data and the code they cannot afford to lose.
Basekick Labs started with telemetry: Arc keeps history in open Parquet on storage you control. Basekick Git applies the same rule to source code, keeping repositories and runners inside your boundary while the collaboration layer sits on top. Both products are built on the premise that the useful thing should outlive the vendor serving it. Built for aerospace and defense first, now running in manufacturing, energy, logistics, finance, and observability.
Arc Enterprise
clustering, RBAC, commercial licensing, and support
Arc Enterprise Managed
we run the database, you run the business
Basekick Git
collaborative source control on your own storage and runners
Migration paths from InfluxDB, ClickHouse, TimescaleDB, and QuestDB
Industry solutions
aerospace & defense, tactical edge, industrial IoT, energy, finance
The rest of the toolbox
A product on its own is not a system. These are the parts that make the rest operable: a console to run Arc from, a CLI, a migration path off InfluxDB, a Grafana datasource, plus a couple of things I built because the problem wouldn't leave me alone.
Self-hosted web console for the Arc instances you run.
SQL console, schema explorer, logs, and monitoring, plus management for tokens, retention, alerts, continuous queries, and MQTT ingestion. Deploys next to Arc with Docker Compose.
LLM-agnostic memory layer for AI agents.
No embeddings, no vector database. Fast, structured, temporal memory that any model can read and write, because most agent memory problems are recall problems, not similarity problems.
Writer-agnostic Apache Iceberg table maintenance.
Compaction, snapshot expiry, and orphan-file cleanup for Iceberg tables, regardless of what wrote them. Open source.
Migrate InfluxDB 1.x and 2.x into Arc, straight off disk.
Reads TSM and WAL files directly, with no running InfluxDB instance required. Checkpointed and resumable, so a multi-terabyte migration survives an interruption.
The Arc CLI, built for operators.
Query, write, import, and manage Arc databases from a terminal or a CI pipeline.
Production Grafana datasource for Arc.
Apache Arrow transport with JSON fallback, full alerting support, and query editing that understands Arc SQL.
Writing
Managed Git hands you an outage you cannot fix and terms that change overnight. Self-hosting hands you identity, certificates, backups, and a pager. Almost nothing sits in between, which is the gap Basekick Git is built for.
This site used to be about coaching. From here it is about founding a company and building a database at the same time: the engineering, the commercial decisions, and the parts I get wrong.