Software that solves
the actual problem.
I build full-stack products end to end: TypeScript and React in the browser, Python and Rust services behind them, and local language models where the data must not leave the machine. I am open to a role at a technology company and to projects for local businesses, and I keep building software under AXONOS.
- Available
- Now
- Looking for
- A role at a technology company, or projects for local businesses
- Based in
- Rethymno · Crete or remote
Things I built
and shipped.
Four projects, described as they are today: three live apps and a booking system.
Open a card for the details.Case study: a system that notices its own failuresWork with me
There is no price list. Every project starts with a short conversation and a written proposal.
One person for software, automation, AI, design and the conversation about how your business runs — so you do not have to coordinate four different providers.
Booking:
how far it goes
One idea in three states — what runs today, what is built and waiting in staging, and what is only possible so far. Each part is labelled honestly.
How it maps to you
The model is specialist → service → time. In a barbershop, the specialist is the barber and the services are the cuts.
- 01SpecialistThe client picks a barber.
- 02ServiceA cut or a shave, each with its own duration.
- 03TimeA free slot in the day; the taken ones close automatically.
How it maps to you
The same model fits one-to-one appointments: the specialist is the professional, the service is the type of visit, and the time is the appointment. Where health data is involved, we decide together from the start what is stored and how it is protected.
- 01SpecialistThe person the client will see.
- 02ServiceA consultation with a given duration.
- 03TimeA free slot; taken ones disappear.
How it maps to you
For repairs, the specialist is the technician, the service is the job, and the time is the visit.
- 01SpecialistWho does the visit.
- 02ServiceThe repair, with its duration.
- 03TimeA free slot in the day.
Limits
- A service price is stored only to show the menu — it is not invoicing or payment.
- There is no model for classes or lessons with a limited number of places.
- The standalone service is not yet live for clients; it is staging code.
If your day runs on people, services and times, this model may fit. Tell me how you book today.
Tell me about your businessHow I work
Ways to work together
Whichever fits, it starts with a written proposal — scope, what is not included, timeline, price and payment terms.
Five kinds of
work I take on.
Each one links to where it is proven. The level next to each tool says how I use it today — not how many years I have held it.
- Daily useTypeScript · JavaScript · Python
- Working levelRust
- LearningGo
Web apps from the interface to the database — React and TypeScript in the browser, Python or Rust services behind them, offline-first where the connection is unreliable.
- TypeScriptDaily use
- ReactDaily use
- Next.jsDaily use
- PythonDaily use
- SQLiteDaily use
- RustWorking level
How I workI map how the work happens today, then build and test the smallest thing that fixes it.
Local AI that runs on my own machine through Ollama, routing across providers, and agents that ask for approval before anything risky — for work where the data must not leave the building, and for trying an idea quickly before anything is built.
- LiteLLMDaily use
- OllamaDaily use
- Retrieval · RAGDaily use
- Local modelsDaily use
- BotsDaily use
How I workAI where it earns its place — and every model answer is validated at the boundary.
Linux, systemd services and timers, backups with restore drills, and monitoring that checks for drift — the machine the apps actually run on.
- LinuxDaily use
- systemdDaily use
- DockerDaily use
- resticDaily use
- Cloudflare TunnelDaily use
How I workChecks are written from failures that actually happened, not from theory.
A booking system with a waitlist and email reminders, a written proposal before any work starts, and everything in Greek and English.
- FastAPIDaily use
- SQLiteDaily use
- OpenAPIDaily use
- EmailDaily use
- Next.jsDaily use
How I workA written proposal first, honest about what is and is not promised — then build with the client.
I look at how a process, a tool or an offer works and find where it loses time or money — including things that look like scams or bad deals — then explain it in plain words and put the options in front of you.
- Local modelsDaily use
- Retrieval · RAGDaily use
How I workI tell you honestly when something is fine, when it is not, and when I am not the right person.
The tools
and where they run.
Pick a project to light up the tools it uses. Every mapping is checked against the source.
Public source: github.com/FrezzaroukosFrontend
Backend
Data
AI
Infra
Testing
How I got here
- 2024
I start building AXONOS on my own — the stack behind my apps, from the database schema to the Linux machine that serves it.
- Anabasis
A public, offline-first training app: 260 commits and 640 automated tests (539 TypeScript, 101 Rust).
- Oxw Nou
My family’s candle shop goes live — catalogue, scent guide and an order request without prepayment.
- Thermidor
A local-first calorie diary with 371 automated tests; everything stays in the browser.
- Booking
A booking system in operation — waitlist and email reminders.
- 24 Feb – 24 Oct 2026
Military service; the systems are maintained and developed remotely throughout. On 15 Oct 2026 I publish the case study from one week of real incidents.
Two doors
A role at a company
Software or AI developer — in Crete or remote. Code review, people who know more than I do, and a product with real users.
Projects for businesses
A slow, manual process in your business — I will tell you honestly whether I am the right person to build the software for it.
Tell me the role,
or the problem.
Email is the quickest way to reach me; the form sends to the same inbox. A role on your team or a slow, manual process in your business — I will answer honestly whether I am the right person for it.