_ _ ______ _ _ ____ _____ | \ | |/ ____| \ / |/ __ \| __ \ .sh | \ | | |__ \ \/ /| | | | |__) | | . \| | __| \ / | | | | _ / | |\ \ | |____ / \| |__| | | \ \ |_| \__|______/_/ \_\____/|_| \_\
A two-person engineering shop. We build the parts of your stack you can't outsource, schedulers, storage layers, custom protocols, and the boring deterministic substrate underneath the AI demo. Mostly Rust and Zig. Some C, when the kernel calls.
We've shipped four production schedulers, two for trading desks, one for a hardware test fleet, one for a genomics pipeline. Per-tenant quotas, work-stealing, replay-from-log for incident review. Written so on-call engineers can read it without a guide.
We build small, embedded storage engines for products that can't ship a Postgres dependency. CRDT-friendly. Snapshot + replication transport written from scratch. Audited by a third party at your option.
Custom wire formats, RPC dialects, and embedded device protocols. Specifications written first, in ABNF, with conformance test vectors. We also rescue undocumented legacy protocols from disassembly when you need to keep talking to a 2007 controller.
Time-boxed two-week engagements: pick the path that's costing you, we profile, we rewrite, we prove the win. Numbers in front of you on day 10. No retainer, no dependency.
2026-06-12 14:02:11 [ok] tiny_kv v0.7 ─ 1,204 tests passed 2026-06-12 14:02:11 [ok] tiny_kv v0.7 ─ fuzz corpus stable (28h, 0 panics) 2026-06-12 13:58:02 [wrn] hotpath:client-22 ─ rewrite finished, awaiting prod soak 2026-06-12 13:41:09 [ok] wire_protocol v1.3 ─ conformance vectors shipped 2026-06-12 13:30:00 [..] custom_scheduler ─ deploy paused for client review window 2026-06-12 12:47:32 [ok] client-09 ─ migration cutover, 0 errors over 4h 2026-06-12 12:14:18 [err] probe:edge-eu-3 ─ p99 spike, root caused to NUMA pinning, fixed 2026-06-12 11:30:00 [ok] nightly ─ all green, ready for tomorrow 2026-06-12 09:02:11 [ok] standup ─ Ada present
# open a ticket, written briefs only, no calls in week one to: hello@nexora.sh subj: [brief] short description of what you need built incl: constraints, budget bracket, current stack, on-call expectations # preferred response window sla: written reply within 2 business days # office hours tz: AST (UTC-4) · CET (UTC+1)
# what we won't take on [x] "reskin our marketing site" [x] crypto/web3 except infra audits [x] staffing/IT augmentation contracts # what gets a fast yes [✓] "our scheduler is choking and we can't see why" [✓] "we need a deterministic replay log" [✓] "this protocol is undocumented, can you spec it?"