The arc connects the dots — and bears the load.
The "arc" in arcodash carries two promises. An arc connects the dots: sources, queries, visualizations, dashboards, alerts, and observability checks, joined in one span. And an arc bears load — it's the structural element you build on, and it holds. Count on your data. Count on the dashboard.
arcodash exists because the classic connect → query → visualize → dashboard → alert workflow — the one a lot of teams already know from older self-hosted query tools — deserved a modern rebuild, with one thing added: eyes on the data itself. The same product that answers "what are the numbers?" also answers "can I trust them?", instead of asking a team to buy, learn, and operate a second tool for that.
It's built on a memory-safe Rust backend and worker, a React 19 front end, and priced one fixed way — no per-seat math, so inviting the whole company doesn't change the bill.
Subscriptions. That's the whole business model.
arcodash costs $200 a month because that's what pays for it. You get 14 days free to decide, and after that it's a paid product — no permanent free tier propped up by something else, no ads, and your data is never the product: arcodash queries your database directly rather than warehousing a copy of it. No investors either, so nobody's clock is running but ours. If the product is useful enough that people pay for it, it keeps getting built. That's the entire plan, and you can see it from here.
What arcodash is not, yet.
- No SOC 2, ISO 27001, or any other certification. The security page says exactly what is in place instead.
- No self-hosted release and no public source yet — the cloud product is the only way to run arcodash today.
- No published uptime SLA and no guaranteed support response time.
- One maintainer. That's the trade you're making, and it's why your data stays in your own database — arcodash caches query results for 24 hours to render them, but never replicates your source — and everything you build exports.