The idea
Every month, accounting firms in Turkey receive their clients' trial balances (mizan) as Excel files, and most of the time those tables stay just a record. Solfe was born to turn the same trial balance into a decision tool: income and expense analysis, personnel and operating costs, VAT, withholding and social security tax analysis, budgets with revisions, and balance sheet and income statement reports, all in one place. Solfe is not an accounting program; it is a decision-support product that reads a trial balance prepared on the Turkish uniform chart of accounts and presents a clear picture to managers and clients.
A database for every firm
The product is built on a multi-tenant architecture. Each accounting firm works on its own subdomain and its data lives in a separate PostgreSQL database, while a separate platform database acts as the control plane for firms, plans and subscriptions. Within a firm, every client company is isolated by its own identity; a request is only ever connected to the firm its address belongs to, and if no match is found the system fails closed. Manager, accountant and read-only client roles, along with per-firm branding, are part of the same structure.
Infrastructure
The application is written in Next.js 16 (App Router), React 19 and strict TypeScript; the data layer runs on PostgreSQL 16 and Drizzle ORM, with separate migration chains for the firm and platform databases. The web app and the background worker are packaged as separate Docker images and deployed on a VPS with Dokploy and Traefik. Traffic arrives through Cloudflare with end-to-end verified TLS, a WAF and bot protection, and the server only accepts connections coming from Cloudflare. Every database is backed up separately each night, and restore-drill scripts make it possible to test the backups.
Security by design
In a product that works with financial data, security could not be an afterthought. Passwords are stored with argon2, two-step verification (TOTP with recovery codes) is supported, login attempts are limited with increasing back-off, and forms are protected by Cloudflare Turnstile. Sessions are re-validated against the database on every request, and password reset links are single-use and short-lived. Security headers such as CSP and HSTS, protection against compression bombs in Excel uploads, redaction of sensitive data in logs and searchable audit records are part of the product as well.
A production line of AI agents
While building Solfe, I set up the working rhythm of a software team with AI agents. I first wrote an implementation plan split into phases, then a roadmap organised in waves of parallel work packages. Each work package went to an agent with its own specification and its own git worktree; while one model wrote the code, a different model reviewed it as an independent auditor. Every wave ended with audit rounds, independent security audits and red-team reports, and the findings were prioritised, fixed and verified again. My role was to be the product's owner, architect and coordinator: making the decisions, writing the specifications, and reviewing and merging the results.
Tests and continuous integration
Every change goes through type checking, linting, sharded and shuffled-order tests, a build, a smoke test, a Docker build and a dependency audit on GitHub Actions, while deployment is a separate, schema-gated step. Tests run against PostgreSQL databases created from scratch on every run, and in the latest releases they reached more than 2,800 tests across 188 files. By parallelising the jobs without loosening a single check, I cut the CI time from about 16 minutes to around 4.
Today
Started in June 2026, Solfe has reached its multi-firm structure, its platform panel and a foundation that has passed security audits, with more than 180 commits and version v0.7.0. The product keeps growing; every new feature is added the same way: plan first, then implementation and independent review.
A trial balance can become a decision tool.