Alexandru Buzi · Camelot Flows
An Avalon for makers, run from Moldova while my son Arthur naps.
I build the site, then I build the staff that runs it. One workshop, no middlemen, fixed prices.
The Name
Why Camelot?
Avalon, in Arthurian legend, is where Excalibur was forged and kept between uses. Not a battlefield — a forge. A vault. The place where the work that makes the work possible gets done quietly, out of sight.
That's what this is: a one-person workshop where strategy, design, and automation are made to order, then dispatched. I named it after my son Arthur, because the day he arrived was the day I decided to build the thing I actually wanted to build.
The Workshop
What I build with.
Two co-equal services. The site is the storefront. The staff is the engine behind it. I do both, so neither gets compromised to fit the other.
Astro, Next.js, GSAP
Performance-first sites with premium animation. Designed to convert, built to load fast.
n8n, Make, Python, Claude API
Workflows that run while you sleep. Lead routing, support agents, data pipelines — built to hold under real load.
Cursor, Netlify, Supabase, Git
Every project ships with clean handoff documentation. You own the codebase. I move fast without cutting corners.
The Calendar
Arthur's nap schedule is my deep-work calendar.
Arthur is two. His nap schedule is non-negotiable, which means mine is too. Ninety minutes, twice a day — that's when the serious work happens. The architecture decisions, the animation code, the n8n flows that need actual thinking.
The rest of the day is communication, review, and the kind of light work that survives interruption. It sounds like a constraint. It's actually a filter: I only take work that fits, which means the work I do take gets done properly.
7:00 – 9:00
Client replies, async reviews, quick fixes.
9:30 – 11:00
First deep block. Architecture, heavy code, system design.
14:00 – 16:00
Second deep block. Design, automation builds, testing.
20:00 – 22:00
Side projects. The game. Writing. Experiments nobody asked for.
Side Project
I'm also building a game.
Not because it pays. Because it's the most effective way I've found to stay sharp on animation, interaction design, and systems thinking. Game dev forces constraints that client work doesn't — and the techniques leak back into everything else.
The parallax on this site started as a game camera experiment. Merlin's dialogue routing started as an NPC state machine. The side project feeds the main work without the main work subsidising it.
- Animation skills maintained at game-dev level, applied to your site
- Systems thinking from game architecture carried into automation design
- A developer who ships creative side work stays technically curious — and that shows in the client work
Location
Moldova is an asset.
Lower cost of living means lower overhead, which means I can take fewer clients and do better work for each one. I don't race to fill a calendar. I pick work carefully and treat it accordingly. The timezone (EET, UTC+2) overlaps fully with Western Europe and reaches US East Coast mornings with an early start.
How I work
The promise.
Every engagement is scoped before it starts. Fixed scope, fixed price, fixed timeline — no retainer creep, no invoice surprises. If scope changes, we agree on it in writing before I touch it.
Every message answered within one business day. If something is blocking you, I unblock it that day.
You know the cost before we start. Scope changes are discussed, agreed, and repriced openly.
Every project ends with documentation. You own the codebase and can have any developer continue the work.