The whole stack, one pair of hands

I'm Shlomi Aflalo — a full stack developer who takes products from idea to production: design, frontend, backend, servers, SEO, analytics. All of it.

Before Celina I spent three years as a full stack engineer in a regulated financial-services environment, from January 2023 to December 2025. Ten projects delivered in Java, Spring Boot, React and Node.js — each one specified, built, tested and handed over to the team that would run it. Since January 2026 I have been building Celina full time. The dates and the employer are on my LinkedIn.

Why hire one developer instead of an agency?

Most solo developers do one slice — the design, or the frontend, or "the WordPress part." Then you become the project manager gluing the slices together. I do the opposite: you describe the outcome, and I own everything between the idea and a live product that Google can find. One person accountable, no handoffs, no "that's the other guy's bug."

At an agency you are not only paying for the building. You are also paying for account management, project management and the overhead around both. Here the same person scopes the project, designs it, writes the code, configures the server it runs on and hands it over. Nothing is lost between the designer, the developer and the project manager, because there is one of each and they are the same person.

One accountable person. No handovers between teams and no argument about whose mistake it was.
A fixed price up front. Not an hourly estimate that drifts as the project runs, but a number agreed before anything is built.
No dependency afterwards. Code, design, domain and data are yours. No license and no monthly fee to keep using what you already paid for.

The proof: two systems in production

Two systems are mine end to end — architecture, database, frontend, servers and deployment — and both are still running in production.

Celina — a live consumer marketplace I founded and built in Lisbon, launched from there in July 2026 and in production since: orders, real-time tracking, KYC identity verification, 100+ Google-indexed SEO pages, automated deploys.
Purchases — a role-based coupon platform (Admin / Company / Customer) in Java 17 and Spring Boot, with token authentication and per-role access control on every endpoint; the same architecture used in e-commerce and digital banking. Source public on GitHub.
Java 17, Spring Boot, React, TypeScript and SQL — the stack both systems above run on, including the architecture, the servers and the deploys.
Not portfolio pieces. Production. Both systems have to keep working with real users on them, which is a different craft from building a demo that looks good in a screenshot.

How I work

The work happens in the open, not behind a closed door. You see where the project stands every week, and you can look for yourself whenever you want.

Directly. You talk to the person writing the code — over WhatsApp, email, or video, in English.
Transparently. Fixed quotes, milestone plans, and a live staging link so you can watch progress instead of reading about it.
In your time zone. I am Portuguese (an EU citizen), and I live and work in Lisbon, on Western European Time — the same working day as European clients, and an afternoon that covers the US East Coast morning.
Face to face where it helps. The kickoff is a video call at a time that suits you. After that everything runs online, on a staging link you can open yourself.
Without lock-in. Domain and hosting are in your name from day one; the rights to the code, design and data pass to you on final payment, with documentation any developer can pick up.
Handed over, not held. That documentation is written for whoever comes next. If you need another developer in two years and I am not reachable, they can carry on without calling me first.

Practical matters

The first questions a client asks are rarely about code. So here are the answers before you have to ask for them.

Invoiced in euros. An itemized invoice, with every line spelled out.
A written agreement before anything is built. Scope, price, milestones and timeline in one document we both sign — and an NDA first if you are about to send me something confidential.
Paid by international bank transfer, in staged milestones on larger projects, so you never pay for work you have not seen.
GDPR from the first line. A cookie notice only where one is genuinely required, analytics that do not load before consent, no third-party trackers you did not ask for, and hosting in a region you choose.
English as the working language. It is the language I write, document and meet in. If the finished product has to run in more than one language, that is routine here: Celina ships bilingual pages, and this site runs in three.

Stack

Frontend: React 18, TypeScript, Vite, HTML/CSS. Backend: Java 17, Spring Boot, Spring Security (JWT), Node.js, Express. Data: MySQL, Prisma, Hibernate/JPA. Infra: Docker, nginx, Let's Encrypt, CI-style deploy pipelines. Growth: technical SEO, structured data, analytics funnels.

This is not a list of technologies I once tried on a weekend. It is what Celina and Purchases are actually made of, servers and deploy pipelines included, and I am the one who keeps them running.

One pair of hands on both ends. The frontend and the backend come from the same person, so the join between them is not a negotiation between two suppliers.
Speed as a starting point. A site that loads slowly on a phone costs you visitors before anyone has seen what you offer.
Measurable results. Analytics and structured data go in from the start, so after launch you can see what is actually happening instead of guessing.

What it costs and what the next step is

The figures below are starting prices in euros. Once you have described the project you get a fixed quote within 48 hours, and I reply to messages within 24. See what each package includes.

One-page personal site — from €1,200.
Landing page — from €1,950.
Business website with technical SEO — from €3,900.
Web application or online store — from €12,000.
A fixed quote within 48 hours. The number is agreed before the work starts, so there is nothing to discover at the end.

Frequently asked questions

Do you work with clients outside the Netherlands?

Yes. I work remotely and in English, invoice in euros, and I am on Western European Time — the same working day as clients across Europe, with an afternoon that covers the US East Coast morning. Where the finished site needs another language, it is delivered in that language.

How do you invoice?

You get an itemized invoice in euros.

Can we speak in person?

The first conversation is a call or a video call, whenever it suits you. After that you follow the work in a staging environment you can open yourself, so you are never waiting on a status email.

Why hire one developer instead of an agency?

Because nothing is lost between the designer, the developer and the project manager: here they are the same person. You pay for the work itself rather than the management layer around it, and you always know who is accountable.

Who owns the code and the data when the project is finished?

You do. Code, design, domain and data go into your name, and you get documentation any other developer can continue from. There is no license and no monthly commitment.

How soon can you start?

Within 48 hours of your describing the project you have a fixed quote, and it says when I can start on the work. I reply to messages within 24 hours.

Work with me GitHub