qaryon is officially launched
qaryon is incorporated, insured, in production, and already billing B2B telecom and pragmatic AI consulting work.
qaryon has moved from a build-in-public project to an officially launched business. The company is incorporated, the SIRET is published, the first services are billed, and the website now acts as the entry point for integrators, operators, and B2B teams looking for senior support on telecom topics.
The positioning remains intentionally simple: independent consulting for carrier telecom, unified communications, SBC, automation, and pragmatic AI. No generic agency posture, no miniature outsourcing company, and no vague AI promise. The objective is to deliver short, scoped, usable engagements, from diagnosis to production.
This journal will document the technical topics behind that work: SIP security, SBC architectures, UCaaS, VoIP automation, observability, and early field notes from the B2B SaaS platform under construction.
For a technical question or a focused need, the entry point is simple: get in touch.
Field note by qaryon
Nicolas Marxer
Enterprise communications solution architect focused on operator, integrator, and B2B deployments.
Need a field view on your communications architecture?
Audit, scoping, or deployment: I work directly on UCaaS, CCaaS, IPBX, SBC, automation, and applied AI.
Discuss a telecom projectRelated reading
Founding qaryon: an idea carried for years, a first client who opened the door
The idea of a structure of my own, I had carried it for years. It took a first client in Switzerland to make it real. The story of founding qaryon.
On a SIP trunk, security is not a deployment option, it is a contractual responsibility
Toll fraud, STIR/SHAKEN, mTLS, SBC hardening. What protects a SIP trunk in 2026, layer by layer, with the configurations and the checklist.
Isolating a VoIP datacenter in broad daylight, without dropping a call
Working on a datacenter during business hours without cutting a customer. The drain runs through DNS, not the SBC: pull the IP, let sessions finish, restore by mirroring. The real trap is the TTL.