New
Platform & App Development
Software, not brochures. User accounts, real databases, dashboards and custom logic, built in Next.js and PostgreSQL. The rule of thumb: if it has to remember who logged in, it belongs on this line.
Built with
Proof
The site you are reading is the proof.
Fair question: how do you know a studio can actually build software and is not just saying so? Everything below runs on this website right now, and you can click most of it yourself.
Payments, one time and recurring
Stripe checkout handling both single purchases and monthly subscriptions, with Apple Pay and Google Pay.
A customer portal behind passwordless login
Clients open /manage, enter their email, and get a signed single use link. No passwords stored, nothing to leak.
Prices validated on the server
The cart price is never trusted from the browser. Every item is re priced server side before payment, which closes a manipulation flaw most small e commerce builds still have.
Rate limiting on every API route
Requests are throttled per client so an endpoint cannot be hammered.
Two languages, one codebase
English and Romanian across every route, with the correct language served automatically and each page indexed separately.
Pages generated from data, not written by hand
On a client project, 45 pages including comparison tables and charts are generated from a single data file. Updating a year of results means editing one entry, not 45 pages.
What that actually means
Starting prices, public like everything else.
Every platform is scoped individually. The starting prices above are real projects, not placeholders.
How a platform project runs
Four stages, paid as they land.
Scope and schema
We map what the software has to do and design the database before any interface exists. Getting this wrong is the single most expensive mistake in a platform project.
Core build
Accounts, permissions, the main engine and the admin panel. You get a working environment to click through, not a status update.
Data and integrations
Bulk import of your existing content, payments if you need them, and anything that has to talk to a third party.
Launch and support
We go live, then stay on. Platforms with real users need monitoring, backups and someone reachable. That is a monthly agreement, priced separately and honestly.
Straight answers
The questions people actually ask before hiring us.
Do you build custom software, or do you use WordPress and Webflow?+
Custom, always. Every site and platform we ship is written in Next.js and React and deployed on Vercel. We do not use WordPress, Webflow or page builders. If a project genuinely suits an off the shelf tool, we will tell you that instead of selling you a build you do not need.
Can you build a database application with logins, custom logic and bulk import?+
Yes. That is exactly what this service line is for. User accounts with roles and permissions, a relational schema designed properly before any screen exists, custom algorithms rather than plugins, and importers that swallow CSV, Excel or PDF.
You are a marketing agency though. Is software really your thing?+
We do both, and we are open about which is which. Presentation sites and campaigns are the volume work. Platforms are the harder work and priced accordingly. The engineering listed above is ours, on our own product, in production.
What happens if I need changes after launch?+
Software with real users is never finished. Monitoring, backups, updates and changes run on a monthly agreement, quoted separately and openly. You are never locked in and you always own your data.
Who owns the code?+
You do, in full, once the project is paid. Source code and every account credential is handed over. We keep the right to reuse generic technical components, never your content, data or brand.
Honest limits
What we do not build.
Tell us what it has to do.
Describe the workflow you want replaced. You get back a scope, a schedule and a fixed price, in writing, before anything is built.
Start a platform project