Skip to content
WalkaisaContact

Idea toproduction,end to end.

I'm Walkaisa, a full-stack developer from Germany. I design, build and run web applications, from interface to infrastructure.

Start a projectView selected work

Available for new projects

01Frontend

Interfaces that feel fast and stay maintainable.

Responsive, accessible web apps built on a typed component system. Server-rendered where it speeds up content, interactive only where something actually changes.

  • TypeScript
  • React
  • Next.js
  • Tailwind CSS
  • shadcn/ui
  • Accessibility

02Performance & Edge

Fast before the first byte.

DNS, TLS, caching and routing configured deliberately. Load time and Core Web Vitals are requirements from day one, not something tuned at the end.

  • Cloudflare
  • CDN caching
  • Reverse proxies
  • HTTP semantics
  • Core Web Vitals

03Auth & Security

Secure from the first commit.

Sign-in, sessions and permissions built on open standards, with least privilege and safe defaults instead of a separate hardening phase.

  • OAuth 2.0
  • OpenID Connect
  • PKCE
  • Session management
  • Access control

04Backend

APIs with clear contracts.

Services in Rust, Go and Node.js, chosen per workload. REST and real-time APIs that are typed, documented and predictable to integrate with.

  • Node.js
  • Rust
  • Go
  • Fastify
  • REST
  • WebSockets

05Data

Data models built to last.

Relational schemas designed around how the product actually queries them, caching for what is hot, and migrations that ship with the code.

  • PostgreSQL
  • MySQL
  • Redis
  • Drizzle ORM
  • Prisma

06DevOps

Shipped, monitored, maintained.

Containerised deployments on Linux, automated pipelines that make releases routine, and monitoring that answers questions when something goes wrong.

  • Docker
  • Linux
  • CI/CD
  • Self-hosting
  • Observability
Scroll to explore my skillsSix disciplines, one developer

00 / 06

About

Curious by default, careful by habit.

I got into software because I wanted to know how things work, and I still build that way: take a problem apart, understand every layer, then put it back together so it holds up for years.

That applies to everything I touch, from a single component to a whole platform. More and more it includes AI: bringing language models into real products with the same care for speed, cost and data handling as the rest of the system.

Interests
Web platforms, AI, self-hosting, developer tools
Way of working
End-to-end ownership, written decisions
Languages
German, English
Open to
Freelance and long-term projects
Download CVSee how I got here

Journey

How I got here.

School, two IT qualifications and a job in software. Next to that, a few side projects that taught me more than I expected.

  1. SchoolSchool diplomaUniversity entrance qualificationFinished school with the qualification to go on to university.
  2. Vocational schoolIT AssistantState-certified qualificationIT fundamentals: hardware, networks, operating systems and my first real programming.
  3. ApprenticeshipSoftware DeveloperVocational training in application developmentTrained as a developer inside a company. Real code, real reviews, real deadlines.
  4. CareerSoftware EngineerCurrent roleBuilding software at an IT and technology company.
  5. NextOpen for workYour project?The next chapter is openIf you have something worth building, I'd like to hear about it.Start a conversation

Side projects

01First users

A side project that got real

I built Incognito, a Discord bot, and it grew to more than 50,000 users across hundreds of servers. Keeping it running every day taught me more about caching, databases and deployments than any course did.

learned Node.js / MySQL / Redis / Docker

See Incognito
02Own tools

Building what I wanted to use

Snapshot started because I wanted my own place for screenshots and videos. nl-market-sdk wraps a marketplace API in one typed client, so the same requests don't have to be written twice.

learned Streaming / API design / TypeScript

See Snapshot
03Today

The whole stack, and AI in it

Today I work across the full stack, from interface to infrastructure, and more and more with AI inside the products I build. One thing hasn't changed: I want to understand every layer of what I ship.

learned Full-stack ownership / AI integration / Operations

See selected work

Selected work

Systems I've designed, built and operated.

Four projects, each owned end to end, from the first design decision to running it in production.

ActiveIdentity infrastructure

Aegis

A self-hosted identity platform built on OpenID Connect. Applications delegate sign-in; administrators manage clients, sessions and access.

It spans the whole stack: OAuth 2.0 flows with PKCE on the backend, a developer-oriented admin interface on the front, and infrastructure that keeps identity under your own control.

Role
Design, development, operations
Scope
Auth flows, admin interface, infrastructure
Standards
OpenID Connect, OAuth 2.0, PKCE

OpenID Connect / OAuth 2.0 / PKCE / Sessions

ActiveSelf-hosted developer tool

Snapshot

A self-hosted upload service for images, GIFs and video, compatible with ShareX out of the box.

Files stream through the service instead of being buffered in memory, checksums are verified on the way in, and the whole thing is built to be deployed with Docker and configured without surprises.

Role
Design, development, operations
Scope
Upload API, storage, deployment
Works with
ShareX, out of the box

Streaming uploads / Checksums / ShareX / Docker-first

ArchivedDiscord platform

Incognito

A multifunctional Discord bot and backend platform that served more than 50,000 users across hundreds of servers.

Moderation, custom commands and automation ran as a long-lived production workload on Node.js and TypeScript, backed by MySQL and Redis and deployed with Docker.

Role
Design, development, operations
Reach
50,000+ users, hundreds of servers
Runtime
One long-running production process

Node.js / TypeScript / MySQL / Redis / Docker

Open sourceTypeScript SDK

nl-market-sdk

An open-source TypeScript SDK for marketplace integration.

OAuth2 and the HTTP API sit behind a typed, reusable client, so integrations start from contracts rather than from documentation.

Role
Design and development
Scope
OAuth2, HTTP API, typed client
License
Open source

TypeScript / OAuth2 / HTTP APIs / Type-safe

How I build

01

Performance is decided at design time.

Rendering strategy, payload size and query shape are architecture decisions, so they are made early rather than tuned late.

02

Security is the starting state.

Authentication, least privilege and safe defaults belong in the first commit, not in a hardening phase.

03

Infrastructure you can rebuild from a repository.

Containers, declarative configuration and pipelines mean any environment can be recreated without memory or luck.

04

Complexity has to earn its place.

Strong types, clear boundaries, and the simplest architecture that solves the actual problem.

Open source

In the open

Live from the GitHub APIgithub.com/Walkaisa
Recent public activity, live from GitHubHover to pause

Testimonials

What it's like to work with me.

Walkaisa is one of the greatest developers out there: He's extremely patient, he's hardworking and he will definitely work things out with you until you're completely satisfied. He's one of the very few developers that's willing to go over and beyond expectations just to fulfill your needs.
AlphaCEO, RevUnityrevunity.com

Contact

Something to build, or something to fix?

Tell me what you're working on. Messages land directly in my inbox, and replies go to the address you leave.

New messageDraft
ToWalkaisa <[email protected]>
0 / 2000