Skip to content
Felix Schumann

The person behind the projects

Curiosity first.Then I build.

I'm Felix Schumann. I turn the things that make me think “there has to be a better way” into tools, products and occasionally entire game worlds.

  • AI engineering
  • Product thinking
  • Made in Germany
A little more about me
Felix, studio portrait
Felix SchumannAI portrait study
59projects to explore
10connected disciplines

Think it through. Make it work.

01 / How I got here

I wanted my own coding platform.

I was tired of PowerShell and terminal-based workflows. So I built IXIOM, my own coding platform. I've put more than 2,000 updates into it.

  1. 01

    Build the workspace I want to use.

    IXIOM is the environment I develop in myself. I want projects, AI tools and the work on the code to fit together. When a workflow slows me down, I can change the platform. My own day-to-day needs are the starting point.

    Explore IXIOM
  2. 02

    Give each job its own specialist.

    With OpenClaw, I organised specialised agents around their own workspaces and memories. Research, review, outreach and creative work each needed a different context. That experience shaped how I think about AI: roles, tools and the handoffs between them deserve as much care as the prompt.

    Inside the Agent Workshop
  3. 03

    Keep improving after the release.

    That same care goes into products such as HandsOff: the first launch, the installation, the next update and recovery when something goes wrong. I use my own tools in real work. It is a direct way to notice the details that need another iteration.

    Meet HandsOff
AI-generated portrait of Felix working at a laptop
I like the moment an idea becomes something you can actually use.
Felix Schumann
AI portrait study / 02

02 / The way I think

Fast to explore. Careful where it counts.

I work across design, code and operations because the experience runs through all three. These habits connect them.

Understand the day before designing the tool.

I want to know where work stalls, what people repeat and which decisions need a human. That is why a CRM gets editable stages, a board gets screenshots at the cursor and a desktop tool gets out of the way. The details come from the task.

In practice: a CRM the team can adapt

03 / What keeps me curious

A few things I keep coming back to.

Play

Worlds with rules of their own.

Games let me explore progression, behaviour and feedback directly. A rule can sound good on paper and feel wrong in play. Browser worlds, NPCs and Unity experiments keep that connection between a system and its experience close.

Enter the game projects
Design

Interfaces with a point of view.

A headline with rhythm, a transition that explains a change, a layout that makes the next step obvious. I enjoy the details that give an interface character. My hero catalogue gives those ideas room to be tried and compared.

Browse the design experiments
Tinker

The tool I wish I had yesterday.

A tray panel, a small time tracker, a better way to find a large folder. I keep building tools for my own working day. Using them is a quick way to find out which details matter and which features can wait.

Explore the desktop tools

04 / Working together

Bring the problem. We'll find the shape.

A real workflow, an idea you want to test or a tool that has become a bottleneck is a good starting point. Here is how I approach it.

  1. 01

    Understand

    Map the task, the people involved and what a useful result would change.

  2. 02

    Make it tangible

    Build a first working version so decisions have something concrete behind them.

  3. 03

    Test the whole flow

    Walk through the experience, including awkward inputs and failure cases.

  4. 04

    Put it to work

    Connect delivery, operation and the feedback that shapes the next iteration.

See the arrangements

What we can build together

  • Agent systems

    Connect models, memory and tools to a real workflow, with clear permissions and a place for human review.

  • Internal platforms

    Build the workspace around the team's day, with connected data and controls people can adapt themselves.

  • Data pipelines

    Turn scattered sources into structured, searchable information through collection, cleaning and enrichment.

  • Desktop products

    Bring the app and its delivery together: installation, accounts, licensing, billing and signed updates.

What I work with

Every technology on this page, and how many of the 59 projects use it.

TypeScript41MongoDB15Rust9Next.js 155Coolify4nginx4Stripe4C#3pgvector3yt-dlp3Canvas2Lua2Vite2Better Auth1discord.js v141Fastify1HLSL1Leaflet1n8n1Node 201Paper API1Prisma1React Native1Riot API1Telegram Bot API1Vercel1
Docker28PostgreSQL15React 198Playwright5Drizzle4Node.js4Tauri 24FastAPI3React3Apify2Cloudflare2SQLite2Zustand2BullMQ1Expo Router1FFmpeg1Java1LM Studio1next-intl1Ollama1Plaid1Qwen1React Three Fiber1ShaderLab1Three.js1xAI Grok Realtime1
Next.js17Python12Next.js 167Tauri5JavaScript4Shell4Traefik4Gemini3Unity3Apollo2ffmpeg2Tailwind v42Architecture1CSS Modules1Expo SDK 571Gradle1Laravel1MySQL1NextAuth1OpenStreetMap1Premiere CEP1React 181Redis1Sharp1Ubuntu1
Felix SchumannFelix SchumannAI automation engineer

Name it, I build it.

If something here looks like the problem you have, write to me. A short description of what is not working is enough to start.