Web apps built end to end.
LucyCloud is a one-person software studio building production web applications — Nuxt and Vue front ends, typed APIs, and the database and cloud plumbing behind them.
- Shipping since
- 2024
- Delivered
- 12+
- Typical build
- 6–12 wks
Independent studio, remote across Europe
Applications, integrations and rescues
From first call to production traffic
What I do
Four things, done properly
Most projects need some of each. Take the whole set, or the one piece your team is missing.
Web applications
Full products, from the first wireframe to the deploy — Nuxt on the front, a typed API and a real database behind it.
What you getFront-end engineering
Design systems and interfaces that hold up: accessible, responsive, and fast on the phone your users actually own.
What you getBack end & data
Schemas that survive the second year, migrations you can run without holding your breath, and APIs that say what they mean.
What you getCloud & delivery
The unglamorous half: environments, CI, object storage, monitoring — so shipping is a habit rather than an event.
What you getSelected work
Things that went live
A few builds in full, from the problem they started as to what they do now.
Shufflescape
A dance school that runs itself
A bilingual platform for a Bratislava dance school: course catalogue and registration, card payments, attendance and lesson tracking, a media gallery, and an admin area the owners run the business from.
Atlas Portal
Fleet paperwork, minus the paperwork
A customer portal for a regional logistics operator: live shipment tracking, document exchange and invoice history behind a single sign-in.
Toolkit
Boring tools, chosen on purpose
Everything here is something I have run in production and can still support two years from now.
- Nuxt
- Vue
- TypeScript
- Tailwind CSS
- Vite
- Node.js
- PostgreSQL
- Supabase
- Redis
- Cloudflare
- Docker
- GitHub Actions
- Vercel
Front end
- Nuxt
- Vue
- TypeScript
- Tailwind CSS
- Vite
Back end & data
- Node.js
- PostgreSQL
- Supabase
- Redis
Cloud & tooling
- Cloudflare
- Docker
- GitHub Actions
- Vercel
How it goes
Four steps, no surprises
You always know what is being built this week, what it costs, and what is left.
- 01
Call
Half an hour on what the thing has to do and who it is for. No deck, no charge.
- 02
Scope
A written plan: what ships, in what order, at what price. You approve it before anything is built.
- 03
Build
Weekly deploys to a preview URL you can click through. Feedback lands in the next week's work.
- 04
Hand over
Production deploy, documentation and a runbook — plus a support window while it beds in.
Have something to build?
Tell me what it needs to do. You will get an honest answer about scope, cost and timeline — including when the answer is that you do not need me.