The freelance EU indie workflow with vikit-cli

Freelance developers in the EU face a unique set of challenges: multiple currencies, VAT handling, GDPR compliance, and the constant pressure to deliver on tight budgets. vikit-cli was designed with these constraints in mind.

Built for the solo builder

When you're a team of one, every tool in your stack needs to earn its keep. vikit-cli is opinionated in ways that matter for the indie developer:

• Zero-config deployment — vikit deploy pushes to either Cloudflare or Fly.io based on your project's needs
• Built-in payment scaffolding — Stripe integration that handles EU VAT out of the box
• GDPR-safe defaults — no analytics, no tracking, no third-party cookies in the scaffold

The workflow

Here's how a typical freelance engagement looks with vikit:

# Monday morning — new client project
npx vikit-cli init client-portal --template saas
cd client-portal

# Add a payment tier
npx vikit-cli add subscription --stripe

# Scaffold the API
npx vikit-cli add route --name invoices --crud

# Push to production
git push origin main  # CI builds, tests, deploys

By Friday, the client has a working portal, you've invoiced them, and you're onto the next project.

Why freelancers choose vikit

The ecosystem of indie-friendly features keeps growing:

• Starter templates for SaaS, marketplace, and content platforms
• Pre-built auth that works with GitHub, Google, and magic links
• Local-first development with vikit dev that starts everything — database, queue, worker — in one terminal

vikit-cli doesn't replace your expertise. It removes the boilerplate so your expertise goes where it matters: into your product.