Open source · 4 projects
The parts of Mintance
you can run without us
Mintance runs on Go and ClickHouse. The pieces that aren't the product — the log shipper, the user-agent parser, the database client — are on GitHub under Apache-2.0 and MIT, in production here, and yours to use. The oldest has been maintained since 2016.
- Repositories
- 04Go, every one
- Contributors
- 17from outside and in
- Stars
- 171159 on the log shipper
- In the open
- 9yrssince 2016
What we maintain
Four Go libraries and daemons, each pulled out of Mintance because it turned out to be useful on its own.
NGINX access logs into ClickHouse, in real time
Tails access logs in text or JSON format, enriches every line with user-agent, bot class and host metadata, then batch-inserts over the native TCP protocol. Disk buffer, circuit breaker and backoff with jitter, so a ClickHouse outage costs you nothing.
- ClickHouse
- NGINX
- At-least-once
User-agent parsing, with AI crawlers named
1,666 detection rules covering browsers, devices and 821 bots — GPTBot, ClaudeBot and Bytespider included. Client Hints support, roughly 500K parses per second per core, zero allocations on a cache hit, no runtime dependencies.
- Bot detection
- Client Hints
- Zero-alloc
A ClickHouse client over plain HTTP
The HTTP interface without the ceremony: context-aware queries, pooled connections, gzip both ways, per-query settings, external data, and cluster mode with ping-based health checks and load balancing.
- ClickHouse
- HTTP
- Cluster-aware
PHP's uniqid(), ported properly
A goroutine-safe unique ID generator for Go, with optional prefixes. Small, boring and running in production — which is the entire job description for a library like this one.
- Goroutine-safe
- Zero deps
Star and fork counts last checked 8 August 2026.
How we work in the open
We didn't build any of this alone — ClickHouse, Go and a long tail of libraries got us here. Publishing back is the cheapest way to settle up.
- 01
The fix goes upstream first
When we hit a bug in something we depend on, the patch lands in that project before it lands in ours. Carrying a private fork is a cost we'd rather not pay twice.
- 02
Permissive licences, no CLA
Apache-2.0 and MIT across the board. Use them commercially, fork them, vendor them into a closed product — there's nothing to sign and nothing to ask us for.
- 03
These run in our production
Every repo here is load-bearing for Mintance, not a weekend demo we pushed and forgot. When something breaks for you, it has usually broken for us first.
Found a bug, or want one of these to do more?
Issues and pull requests are read by the people who wrote the code. If GitHub isn't your thing, email works just as well: opensource@mintance.com.