I build AI, robots and rockets.
I'm Neo, founder of NeoLabs in Germany. Self-hosted agents, a delivery robot for the house, and launch controllers built around safety.
See the workMost of my work starts the same way. Something should exist, it doesn't, so I build it.
The personal AI agent you host yourself. It keeps working after the chat ends.
Its own computer, a memory, a schedule and a voice, on your hardware, with the model you choose. It runs a private Linux desktop you can watch or take over, and it asks before anything risky.
- Triggers42, from new mail to Home Assistant
- Channels24, including WhatsApp, Signal and Matrix
- DevicesIts own Android emulator, your desktop, an ESP32 wearable
- Runs onDesktop app, Docker or one script
Every Monday: get me to Berlin by Tuesday, 10:00.
Window seat. No tight changes.
Compared three connections on its own desktop.
Booking costs money, so it asks first.
Booked, using a login the model never sees.
Sent you the ticket.
Nothing booked. It asked you what to change.
Every model. One endpoint.
Connect any inference provider, from free tiers to paid APIs and your own servers. It checks every key, imports every model and sends each request to the best one right now. Errors and slow answers earn penalties. Failures fall back silently.
- Providers80+, plus any custom endpoint
- APIsOpenAI Chat, Anthropic Messages, OpenAI Responses
- BudgetsFree-only keys never touch a paid model
- PrivacyOnly request metadata is logged, never prompts
Recorded anywhere. Yours everywhere. One conversation becomes exactly one memory.
A self-hosted audio memory that takes web, desktop and wearable clients. It tells speakers apart on your machine with 31 MB of models, and silence is never sent anywhere. Clients hold every chunk until the server proves its transcript is durable.
- OfflineClients buffer and resume idempotent uploads
- InferenceReplaceable. Bring the provider you choose
- RecallFrom NeoAgent, or over MCP in any client
Can we move the review to Thursday?
Thursday works. I'll send the notes.
Good. And order the new motor driver.
On it.
Review moved to Thursday. Notes coming. Motor driver being ordered.
A delivery robot for the house. It maps the floors, drives to a place, waits, and comes back.
When it reaches a door it stops and asks someone to open it. It also wants to be petted. Underneath, it is a study in what should happen when things fail.
- DriveTwo hoverboard hub motors
- SafetyESP32 owns motors, brake and e-stop, so Linux can die mid-drive
- BrainRaspberry Pi 5: LiDAR, route following, camera, speaker
- LinkBluetooth nearby, LoRa over Meshtastic when not
Bereit
Ready. Waiting for the next job.
Motion is a lease, not a state.
A drive command lasts 1000 ms. Keep sending heartbeats or the wheels stop, with nothing having to detect the failure.
No lease. Wheels locked.
- Connect
- Checklist
- Arm
- Count
Connect once. BLE drives every view.
A laptop at the launch site talks to a custom ESP32 board.
Nothing arms until it's GO.
Arming is deliberate. Hold to arm.
Press and hold. Let go early and nothing happens.
Link heartbeat every 700 ms
Ignition. On a real pad a phone is filming this with the countdown on its HUD.
A launch controller built for safety first, and rockets to go with it.
A one-layer PCB with no bridges, a mission dashboard, and a guided flow from connect to countdown. Live weather and aircraft checks give a GO, HOLD or NO-GO. It even scores launch sites against roads, power lines and airports.
Schematic to PCB, firmware to backend, API to the interface someone actually uses. I like owning the whole thing.
- Self-hosted AIAgent runtimes, memory, MCP, tool orchestration
- Full stackNode.js, Python, Flutter, SQLite, Docker
- EmbeddedESP32 firmware, BLE, LoRa, custom PCBs
- Robots, flightNavigation, teleoperation, safety interlocks, launch control
Open to collaboration, contract work and interesting hardware problems.