Publisher
What we publish
qb, a C++20 actor framework, and the protocol modules around it: HTTP, WebSocket, PostgreSQL, Redis. Written for throughput, maintained because we run them ourselves.
Intelligent System Network Development
We build software that has to keep running.
A Paris software studio with two halves: the open-source systems software we publish, and the platforms we design, build and operate for organisations whose requirements have outgrown off-the-shelf tools.
Paris studio, working internationallyPublishing open source since 2013Regulated and high-load environments
Two halves of one practice
The code we publish is the code we deploy. Client work pays for it, and publishing it is how anyone can check what we build on.
Consulting
What we deliver
Back-office cores, integration between systems that were never meant to meet, reporting a regulator will accept, and AI features that inherit the obligations your data already carried.
What changes once it ships
Four outcomes we are willing to be measured on.
Numbers you can act on
One set of figures for operations and for the board, refreshed on a schedule you choose, with a warning when a process drifts instead of a discovery three weeks later.
Shorter cycles
Workflows people stop re-keying, approvals that follow the path the team already uses, and fewer handoffs between systems that should have been talking to each other.
Data that survives an audit
Explicit contracts between domains, lineage you can walk backwards, and exports that reconcile with what the operational systems actually hold.
A security review you pass
Access control, an audit trail, and AI features built under the same data-protection rules as everything else. Written so a security officer can sign rather than merely tolerate.
The same people, from brief to on-call
Architecture, data, security, cost and operations stay coherent because the engineers who decided them are the ones carrying the pager.
We are still there for the integration tests, the regulator's questions, the model that drifts, and the traffic that arrives early.
2013
our first public repositories
14
public repositories, open to read and to fork
3
working languages: French, English, Spanish
Where our engineers have worked
Not a brochure claim: the industries our people came from before ISNDEV, and the kind of system they were building there.
Finance & insurance
Policy and claims cores, regulatory reporting, payment supervision. Systems where a rounding rule is a legal question.
Health & life sciences
Care pathways and laboratory operations, where a record has to stay traceable years after the person who entered it has moved on.
Culture & media
Ticketing and audience platforms that meet a year of traffic in one afternoon, with a back-office that keeps up.
Retail & logistics
Stock, fulfilment and e-commerce cores, at the point where a spreadsheet and three tools stop agreeing with each other.
Energy & large operators
Contract and supplier governance, and administrative processes that were paper at a scale where paper stops working.
Public sector & institutions
Citizen-facing procedures and the reporting behind them, where the audit trail is the point rather than a feature.
An engagement has gone well when the client's own team can operate the system, and the runbook answers the questions we used to answer by phone.
The code is public. So is the issue tracker.
Every repository carries its history and its open issues. You can see what we chose, what we got wrong, and how long we took to fix it. That is harder to stage than a case study.
github
qb
The framework. Share-nothing actors over a non-blocking I/O runtime, with native C++20 coroutines. The I/O layer stands alone if the actor engine is more than you need.
Visit the qb sitegithub
qbm-http
HTTP/1.1 through HTTP/3 and WebSocket behind one router — servers and clients written as actors.
github
qbm-pgsql
PostgreSQL’s wire protocol spoken directly over a socket, rather than wrapped around a client library.
Tell us what has to be true in six months.
Write a paragraph: the users, the constraint, the deadline. We answer serious briefs within a few working days, and we say so when we are the wrong studio for the job.