Skip to content
Solventist

Software studio — Turkey

Most teams describe their work.
We measure ours.

Industry-specific business systems — API, web and mobile, from one team.

See the workStart a conversation
61 ms50 sales on a till with the network cable pulledWritten to the local database; the network was never waited on.
51/51Events accepted by the server once the cable went back in0 rejected, 0 retries, queue empty at the end of the run.

What we build

We build business software shaped around how a company actually works. The backend, the web panel and the mobile app come from the same team. We host what we build, and we maintain it.

  1. Backend and API

    Where the business rules live. Multi-tenant data isolation, a role and permission matrix, authentication, a versioned API surface and a consistent error contract. Calculation stays in exactly one place on the server: write the same arithmetic twice and you will eventually quote two different prices.

    NestJS · TypeScript · Prisma · PostgreSQL

  2. Web applications

    Admin panels and corporate sites. Server-rendered pages, real multilingual routing, and performance we measure rather than assume. Every field a panel shows has already passed a permission check on the server.

    Next.js · TypeScript · React

  3. Mobile applications

    iOS and Android from one codebase. Three things go into the first release or never: a forced-update check, a versioned API and feature flags. None can be retrofitted, and without them the old builds sitting in the stores dictate your roadmap for months.

    Flutter · Dart · FCM

  4. Deployment and infrastructure

    How code reaches the server is part of the job. Each client gets its own database and its own database user. Backups live with a second provider and are restore-tested — an untested backup is not a backup. Nothing is pushed straight to the main branches: pull request plus one approval, with every request checked by CI.

    Docker · Coolify · Cloudflare R2 · GitHub Actions

Services
Live demo

Run the engine yourself

Change the size, the system and the glass; every intermediate step, from profile length to margin, recomputes while you drag.

The calculation below was performed on the server as the page was built. With JavaScript it becomes draggable; the numbers do not change, they just go live.

3,600 mm
2,400 mm
System
Glass

Total

Profile length
12.00 m
Profile cost
14,880.00 TRY
Glass area
8.64 m²
Glass cost
6,220.80 TRY
Labour and installation
6,220.00 TRY
Subtotal
27,320.80 TRY
Margin
7,649.82 TRY
Total
34,970.6240000000 TRY

The catalogue and unit prices are synthetic. What is real is the calculation between them: this same engine produces quotes across a manufacturer's dealer network, and its output matches the manufacturer's own spreadsheet to ten decimal places.

Where we work

Four fields, and a working system behind each one.

Building products — glass balconies, guillotine and sliding systems
A multi-tenant B2B system for a manufacturer’s dealer network. The dealer measures on site, picks the system and the glass; the application computes cost and sale price, produces the quote, and the job is then tracked through production, installation and delivery. The heart of the product is not a screen — it is the calculation engine.Two manufacturers
Retail — grocery store automation
Till, stock and a central panel. The till keeps selling with no connection at all; when the link returns, the queued sales go up to the server in a single batch. The installer is downloaded from the web — no technician visit.Our own product
Retail — the consumer side
An app for finding discounted products in nearby stores. Location-based queries, maps, store and product listings; the interface works in two languages.One mobile app
Manufacturing — doors and CNC production
A mobile app with a product catalogue, an ordering flow, payment and an admin panel — including card payments through Turkish providers and push notification infrastructure.One mobile app
All industries

How we work

Six steps. We write down what happens at each one, what we need from you, and how long it takes — because the most expensive surprise in a software project is an expectation discovered late.

  1. 01Discovery
    What we do
    We look at how the work runs today: who does what, where the spreadsheets live, which data is still typed in by hand. This step is not about software. It is about understanding the job.
    What we need from you
    One person who genuinely knows the process, and the files you use today — spreadsheets, forms, screens from your current software.
    How long
    Depends on how much process there is to look at. You leave this step with a written summary.
  2. 02Scope and fixed quote
    What we do
    We put what will be built — and what will not — into a written scope, with a fixed price and a delivery date. What is out of scope is stated as plainly as what is in it.
    What we need from you
    Read the scope and approve it. This document settles most of the arguments that would otherwise arrive at the end of the project.
    How long
    The delivery date is set here and written into the quote.
  3. 03Development in two-week rounds
    What we do
    We build in two-week rounds. At the end of each one you get something that runs — not a screenshot, a version you can open and use.
    What we need from you
    Half an hour at the end of each round: try what you were given and say what is wrong. A mistake caught early is cheap.
    How long
    Rounds are two weeks. How many there will be is written in the scope.
  4. 04Testing and acceptance
    What we do
    We set the system up with your own data and fix what breaks. The acceptance criteria were written into the scope before we started.
    What we need from you
    Try it with your own data. Acceptance is your call — we do not get to declare the work finished.
    How long
    As long as your sign-off takes.
  5. 05Going live
    What we do
    Hosting, domain, certificates and the first install are ours. Mobile apps are published from your own store account.
    What we need from you
    Access to the domain and the store account. You never touch the server.
    How long
    Store review time is not ours to promise; everything either side of it is on us.
  6. 06Maintenance and support
    What we do
    Monthly hosting and maintenance: updates, backups, monitoring and certificate renewal. Backups are encrypted and kept off the server, and restores are tested.
    What we need from you
    Tell us when something new is needed.
    How long
    Monthly, for as long as the agreement runs.

Case studies

Both are written the way engineers read: problem, approach, evidence.

Retail — grocery store automation

A till that keeps selling when the line goes down

Point of sale, stock and a central panel for small and mid-sized grocery stores. The till sells with no network at all; when the connection returns, the queued sales reach the server in a single request and none are lost.

  • Go
  • TypeScript
  • Electron
  • React
  • Next.js
  • SQLite
  • PostgreSQL
  • Docker
Read the case

Building products — glass balcony and guillotine system manufacturing

Turning a pricing spreadsheet into a quoting engine

A multi-tenant B2B application for the dealer network of a glass balcony, guillotine and sliding system manufacturer. The dealer measures on site and picks the system and glass; the server computes cost and sale price, produces the quote, and the job is tracked through production and installation.

  • NestJS
  • TypeScript
  • Prisma
  • PostgreSQL
  • Next.js
  • Flutter
  • Docker
Read the case
See all work

Why us

A young studio sells its method, not its history. What follows are rules we apply, not slogans.

  • One team, three layers

    The API, the web panel and the mobile app come from the same team. An integration problem between layers cannot get lost between two suppliers — someone owns it.

  • We host it

    The server, the backups, the monitoring and the certificates are our job. You never touch the server, and you never have to.

  • Every client isolated

    A separate project, a separate database and a separate database user. One client’s data never meets another client’s query.

  • No data without off-site backups

    We do not host client data without encrypted backups kept off the server. The backup alone is not enough either: restores are tested, because an untested backup is not a backup.

  • The app is yours

    Mobile apps are published from your own store account. If you ever leave, the app stays with you — it is not held hostage in ours.

  • A standard stack

    The same technologies on every project: NestJS, PostgreSQL, Next.js, Flutter. Your system stays maintainable even if the people change, and nobody gets locked in by an exotic choice made for one job.

Who you are dealing with

You do not know us. So instead of adjectives, here is what you can check.

Location
TurkeyOne to two hours ahead of Central European Time; our working day covers yours end to end.
Working languages
English · TurkishQuotes, technical correspondence and handover documents run in both.
Who you talk to
The people who write the systemFrom the first email. No account manager in between, no subcontracted team.
Stack
NestJS · PostgreSQL · Next.js · FlutterThe same on every project. Nothing exotic picked for a single job.
Hosting
Our own serverSetup, certificates, monitoring and backups are ours; you never touch the server.
The numbers here
Measured, not estimatedEvery figure has a dated run report behind it, and you can ask which one.

You will not find a client name here. We name the work by its industry; who commissioned what is not ours to publish — and for the same reason your name will not appear on another client's site. You will not find percentages, savings or user counts either: we do not print numbers we have not measured. One sentence that collapses on the first phone call costs more than ten good references.

Measured results

Not marketing copy — run output. Each line is backed by a dated report.

61 ms50 sales on a till with the network cable pulledWritten to the local database; the network was never waited on.
51/51Events accepted by the server once the cable went back in0 rejected, 0 retries, queue empty at the end of the run.
53 endpointsSurface of a multi-tenant B2B API88 unit and 195 end-to-end tests, all passing.
10 decimalsPricing precision of the calculation engineIt reproduces the manufacturer’s own spreadsheet digit for digit.

Every number on this site comes from one of our own run reports. Nothing here is an estimate.

Let us scope the next system

Send us the problem and we will come back with a scope. An engineer answers the first message, not a sales rep.

[email protected]
Contact