Geneva, Switzerland — CH-1200
Lixsady designs, hardens, and operates the systems behind serious projects — from bare-metal networks to the software running on top of them. One team, four disciplines, no handoffs.
Who we are
Lixsady is an infrastructure and development company based in Geneva, Switzerland, operating under lixsady.ch. We work directly with founders, studios, and small teams who need infrastructure that won't wake them up at 3am — and software built by the same people who keep it running.
The firm is organized around four disciplines that feed into each other: we plan systems the way we'd want to inherit them, build software with deployment in mind from day one, and treat security as a design constraint rather than an afterthought. Lixsady operates out of Geneva with a secondary footprint in Miami, Florida, and maintains an open-source presence on GitHub as @lixsady.
Currently shipping
Everything Lixsady and Lixvera are building right now lives on one index — from route-planning tools to notification systems still taking shape.
Sub-brand
Tester accounts get early access to Lixvera projects before public release. Help shape what ships by trying builds early and sending feedback straight to the team.
Services
Four disciplines, one team. No capability listed here is theoretical — all of it is in active use across current Lixsady projects.
Ongoing operation of servers, VPS environments, and network topology — provisioning, monitoring, patching, and capacity planning so systems keep running quietly in the background. We work across Linux distributions, containerized deployments, and control panels like aaPanel, and we document everything so nothing lives only in one person's head.
End-to-end build work across web platforms, native and cross-platform apps, interactive 3D, and game systems. We favor small, legible stacks over frameworks-for-their-own-sake — enough structure to move fast, little enough that someone else can pick it up in an afternoon.
Configuration review, attack-surface reduction, and access control across servers and applications, plus the less glamorous work of compliance — Swiss FADP and GDPR posture, disclosure templates, and the legal groundwork that protects a project once it's live.
Hosting for the projects we build and for infrastructure-only clients — uptime monitoring, backups, access logging, and a direct line to the people who set it up, rather than a ticket queue.
The stack, by layer
Everything between the public internet and a shell prompt: encrypted admin paths, edge routing, certificates, and the tooling used to verify all three.
Linux hosts and the services running on them, whether bare on the host or containerised. Panels where they save time, plain config files where they don't.
Application databases, backups that are actually restored and tested, and a record of who touched what.
What gets built on top — web front ends, mapping and route tooling, cross-platform apps, and game-server resources.
The unglamorous half of keeping something alive over years rather than weeks. Written down, so it survives a person being unavailable.
The paperwork that protects a project once it is public, handled alongside the build rather than bolted on at launch.
Network
Two offices and the machines they look after. Every server is the responsibility of a named office — not a shared pool and not a rotation, so you always know who to reach.
Select a marker to see what it is and which office runs it.
| Location | Role | Managed by | Contact |
|---|
Project index
A running index of what Lixsady and Lixvera are building — from infrastructure tooling to apps still taking shape. Client and service work lives under Services.
Open a GPX file to inspect the track, edit and reorder waypoints, trim or split segments, or draw a new route from scratch on the map — then export a clean file for a device or another app. Built for the kind of trip planning where the route matters more than the software. Runs on nginx, PHP 8.3 and MySQL at gpx.lixsady.online; access is gated to Lixvera testers while it is in beta.
A drop-in NUI notification resource for FiveM servers. Server scripts fire a single call and lx_notify handles the queue, placement, and dismissal, so alerts behave the same way no matter which resource raised them. Themes live in one config file, so a server can match its own identity without forking the code, and admin channels are gated separately from player-facing ones.
An Android app for the pile of notifications a phone accumulates over a day. Group them by app, mute the sources that only ever interrupt, and keep the ones that actually matter reachable instead of buried. Built with Expo and React Native, published under ch.lixsady.lixalert.
A fishing log built around place. Record what you caught and exactly where, then look back across seasons to see which spots actually produce and which ones you keep returning to out of habit. Live at catchregistry.com.
A personal health summariser. Point it at an export from a wearable or health platform and it reads the raw record — sleep, activity, resting rates, trends running across months — then writes back a plain-language summary instead of another wall of charts. The goal is to make a year of your own data legible in a couple of minutes. It summarises what your data already says and is not a diagnostic tool. Currently in closed beta for Lixvera testers.
Secure, contained virtual storage with region pinning. Each store is isolated rather than carved out of a shared pool, and you choose which region the data physically sits in — which matters when a contract or a regulator says it cannot leave a jurisdiction. Runs on the same node network listed under Network.
Sub-brand
Lixvera is Lixsady's sub-brand for work that sits slightly outside the core infrastructure practice — experimental builds, consumer-facing products, and projects that warrant their own identity while still running on Lixsady's operational backbone.
Tester accounts get early access to Lixvera projects before public release. Help shape what ships by trying builds early and sending feedback straight to the team.
Apply
Tell us which projects interest you and what you would be testing on. We confirm your email first, then a person reads the application.
If that address can receive mail, a confirmation link is on its way. It works once and expires in an hour. Your application reaches the review queue as soon as you click it.
Get in touch
Tell us what you're building or what's currently on fire. We read everything that comes in and reply from Geneva, usually within a business day. For anything tied to a specific server, the office that manages it is listed under Network.
Prefer to write your own? Download the email template.