ἄναρχος · without a ruler

Decided hereBuilt here

Planning, architecture, code, deployment, operations. None of it is handed off. Intent is not whittled down between the decision and the code. Understanding the problem is part of the build, not a prerequisite for it.

BUILT WITH

  • Languages
  • Java
  • Kotlin
  • JavaScript
  • TypeScript
  • Python
  • Backend
  • Spring
  • Spring Boot
  • Node.js
  • Express
  • FastAPI
  • Django
  • Flask
  • Frontend
  • React
  • Next.js
  • Vue.js
  • Tailwind
  • Three.js
  • Data
  • MySQL
  • MariaDB
  • PostgreSQL
  • MongoDB
  • Redis
  • SQLite
  • Elasticsearch
  • Infrastructure
  • Docker
  • Kubernetes
  • Nginx
  • Linux
  • Ubuntu
  • Vercel
  • Supabase
  • Firebase
  • Build & CI
  • Git
  • GitHub
  • GitLab
  • GitHub Actions
  • Jenkins
  • Gradle
  • Maven
  • AI
  • PyTorch
  • TensorFlow
  • Anthropic
01

The work

AI speaking practice

Reheview

Speaking does not get better for lack of a partner. It stalls because a conversation ends and leaves only the sense that it went badly, not what actually happened. Reheview keeps what you just said so you can look back at it.

Not launched yet · Get notified

Not public yet

Shown after launch

02

What can be done

01

Full-stack development

Front end, back end, infrastructure, deployment. One person carries it to the end. When something breaks, no time goes into working out which layer owns it.

02

AI engineering

Attaching a model is not the finish line. The model gets built into something that actually runs and keeps running. A demo and a product are different things.

03

Product design

The work starts before the spec, with deciding what to build. Commerce–ERP integration, a bulk messaging platform, legacy system migrations.

03

What you can hand over

  • 01Automation that speaks up when it stopsWork people repeat by hand runs on its own. When it stops or fails, you hear about it right then. Small jobs are a fine place to start: a crawler, scheduled sends, order alerts.
  • 02Claude Code and MCP setupA team gets Claude Code working on its real repositories. CLAUDE.md, permissions and MCP server connections, with the reason for each choice written down.
  • 03Document chatbotsHow often the right document comes back gets measured, and that number ships with the bot. “Seems to work” is not where it ends.
  • 04Admin tools and API integrationsSpreadsheet work moves into an admin page. When a call to an outside service fails, the request is not lost. It goes out again.
  • 05Systems you inheritedCode someone else wrote, or a service put together quickly with AI, brought to a state that can be run in production. Server moves and failure alerts included.

How a project runs and what it costs is on the contact page.

04

How the work happens

  • ANobody in betweenNothing stands between the decision and the work. What gets decided today is in the code today.
  • BReasons get written downTwo or three alternatives go side by side, and what was weighed against what is left in writing. Six months on, whoever reverts it needs that.
  • CBuilt to the endFirst line to last, written here. It does not stop at a demo. It goes until it is running in production.
05

The name, the person

The Greek ἄναρχος joins ἀν- (without) to ἀρχή, a word that means ‘the very beginning’ and ‘rule’ at once. The prefix removes both: nobody rules it, and nothing comes before it.

The name came second. The decision came first: no one above, no company above. Greek already had a word for exactly that.

“Not my area” is what you say when there is someone to hand the problem to. Here there is not. Some problems fall between disciplines and nobody claims them. Those are the ones that end up here.

KIMSUNGWOO 김성우 FULL STACK DEVELOPER
AI ENGINEER
06

Get in touch

If there is something to build together, say so. Any question is fine too.

Send a note