gioser
critical systems architecture
I'm Sergio Velásquez Zeballos.
I build from the underlying mathematics all the way to production,
with no magic dependencies and no patches in between.
Gioser is my operating matrix.
I design the complete system: domain, data, interface, deployment. A single counterpart from the first sketch to the first real invoice. For problems that no longer fit in an off-the-shelf SaaS.
AI that understands your business, not flashy demos. I integrate language models, embeddings and agents into the operational flow, measuring cost, latency and quality like any other component.
Reproducible, auditable platforms, deployable on your own cloud or servers. No magic dependencies. If tomorrow you have to migrate, you migrate.
Diagnosis precedes implementation. Every architecture decision is a priorities decision in another language — and it gets made with the business at the table, not afterwards.
Short cycles, concrete artifacts: a demo, a deployment, a load test. What gets delivered can be touched. No intangible roadmaps, no PowerPoint milestones.
The system is delivered documented and operable. No lock-in. You are the absolute owner of your infrastructure from day one — binary, source, keys, manifests.
Closed cost per phase. Zero open-ended time & materials. Zero drift. The estimate is a contract, not an aspiration.
These are not prototypes or mockups: they are pieces that compile, that run on real machines and that anyone can read line by line. Everything below lives in two open codebases — tawasuyu (822 Rust modules, ~733,000 lines) and hammer (the operating system and its catalogue of 769 programs). Every figure on this page can be checked against the code, today.
Every component is born from its unique cryptographic fingerprint. If something gets corrupted, you notice instantly; if something breaks, it rolls back in one command. Programs don't ask for permissions: if a capability wasn't granted and signed, the door doesn't even exist in the system. An organization's most critical infrastructure deserves this level of guarantee, not a backup script and crossed fingers.
In-house kernel of ~20,000 lines · boots end to end · 20 applications isolated from one another · read the project
A distribution that compiles every program from source, in isolation, and stores the result under its fingerprint. Compiling twice yields the same binary, byte for byte: if a third party rebuilds the same thing and it doesn't match, something was touched along the way. On top runs a channel through which an artificial intelligence understands the system, proposes changes and applies them — with a safety net: tried aside, confirmed by hand, and every change recorded and reversible in one command. The distance between someone who has never opened a terminal and someone who maintains their own operating system disappears.
769 programs compiled and sealed · the Rust compiler and the Linux 6.16.12 kernel rebuilt from scratch, with no third-party binaries · full KDE desktop hydrated · read the project
An in-house renderer that paints straight onto the GPU. It makes it possible to build interfaces the browser cannot sustain — complex editors, living canvases, high-volume visualizations, three-dimensional worlds — with the fluidity of a video game and the precision of a printing press. It is the foundation every application on this page is built on.
70 ready interface components · in-house 3D engine · first Android APK compiled from that same code, with nothing rewritten · read the project
The program that draws the windows, splits the screen and handles keyboard and mouse. It is not a theme on top of someone else's desktop: it is the desktop. Multiple monitors, sessions that resume, configurable shortcuts and whichever look the user prefers. Where others integrate, here we build — which is why there is no foreign layer to audit, update or charge for it.
Daily driver · it is what the rest of the suite is built on · read the project
A single document coexists with its translations, tones and summaries; when the original changes, its derived versions mark themselves stale and regenerate with one button. AI is one more thread, not the conductor — and the provider can be swapped without touching the document. Built for publishers, legal teams and living archives.
Translate, summarize, shift tone, and compare two documents as if they were layers · read the project
A page engine written from scratch: it parses the HTML, applies the CSS and runs the JavaScript of real sites — the one in the image is this very project, seen through it. It matters when the web stops being something you look at and becomes something your organization processes: pulling data out of portals, automating paperwork, auditing what a site executes before letting it run.
In-house style and JavaScript engines · third-party scripts run in a cage the user authorizes · read the project
Real double-entry accounting, an in-house spreadsheet with formulas, invoicing adapted per country through a rules file — not through a different build of the program. It runs on the company's own server: the books don't live in anyone's cloud, and the day you want to migrate, they come out in open formats.
Journal, ledger and balance sheets · Excel import and export with verified round-trip · read the project
Your identity isn't kept by Google or Microsoft: it is kept by you — cryptographically proven, transferable between machines, valid on any network willing to recognize it. With it you sign concrete, revocable permissions — who may run what, and until when. Designed for communities and organizations that need to operate outside the umbrella of the big platforms.
Sovereign keys already issued and in use inside the operating system · read the project
A laboratory where language models, personal records and daily practices converse in real time. The public experiment of how an AI can accompany thought without replacing it. It also serves as the proving ground for what we offer clients.
Notes that sync between machines with no central server · read the project
The deep disciplines — clinical psychology, contemplation, fine neurophysiology — don't need more slogans. They need instruments. Recording apparatus, reproducible archives, falsifiable models. Building that foundation so the old questions can find their experimental counterpart, without dissolving into self-help or surrendering to reductionism.
Hypotheses that don't depend on foreign licenses or on platforms that change their terms tomorrow. Sensors, simulators, scientific databases operated locally — sovereign, reproducible. If the experiment depends on the vendor, so does the conclusion — and nobody is going to audit the vendor.
Graphics renderers, verifiable operating systems, robust cryptography, natural speech synthesis. Frontier technology deployed where it's most needed, not where it bills best. A cooperative should be able to operate the same things a bank operates; a rural school, the same as a university lab.
A farmer with his archive. A doctor with the clinical record that travels with her. An activist with his private network. A neighborhood council with its own cloud. Sovereignty not as a flag or a speech — as everyday infrastructure, small, walkable, that turns on when the lights come on.
The words code is named with are not neutral. A variable called khipu organizes memory differently than one called record. Building from one's own categories — from the south, from the countryside, from the deep traditions — is an act of engineering as much as a political one. What passes through the repository decides what survives.
Tell it with the precision you'd use with a technical peer — the critical problem you need solved, the infrastructure you want to stand up, the technology that keeps failing. If what you describe calls for deep engineering, we schedule a technical session.
