Case · public code
Open-Source Code: What You Can Read and Run
Much of our work is under NDA and cannot be shown. So we keep our own projects public, where you can see how we write code, tests and documentation. Below is each project with its purpose and an honest statement of maturity.
02On maturity
How to read this list
These are demonstration and research projects. They show our approach and implementation quality, but they do not replace production solutions and we do not position them that way. For each project we say what it does and what not to expect from it.
03Projects
Public projects
RivetPDF
A native PDF editor in C++. Shows work with the document format and a native interface. Repository: github.com/Husqvarnalox.
execute-once
A reference architecture for “effect exactly once”: reproducible reliability tests with duplicate events, relay failures, p95 and p99 metrics and invariant checks. github.com/Husqvarnalox/execute-once.
sandboxd
A Go daemon for process isolation: Linux namespaces, cgroup v2, seccomp, a bounded scheduler, an HTTP API, SSE logs and Prometheus metrics. Experimental, not a ready commercial container engine. github.com/Husqvarnalox/sandboxd.
InterScale (InferScale)
Our own inference runtime: batching, KV cache, token streaming, request cancellation, metrics. A research project, not positioned as a vLLM replacement. Repository: github.com/Husqvarnalox.
wildberries-tariff-sync
A TypeScript service that syncs Wildberries tariffs into PostgreSQL and Google Sheets. An example of turning a manual process into an automated one. github.com/Husqvarnalox/wildberries-tariff-sync.
04What it shows
What you can judge from them
Work on correctness
execute-once shows how to verify delivery guarantees by running them, not by describing them.
System level
sandboxd and InterScale demonstrate work with isolation, scheduling and resources.
Native development
RivetPDF shows C++ and work with a document format.
Applied automation
wildberries-tariff-sync shows the path from a manual export to a service.
Want to discuss the code or a task?
If these projects show how we work, describe your task. We will answer plainly.
Get in touch06Contact
Tell us what
has to work.
Describe the problem, your current system and its constraints. If it’s a good fit, we’ll suggest a next step — usually a short call about data, integrations and timelines.
- Telegram@missuk2003
- Emailceo@closeflow.ru
- GitHubHusqvarnalox