Skip to content
LokumTech.

A boutique software studio

Akaunting, installed and maintained. Plus the internal software your team is currently running in spreadsheets.

We build and run Esimbit, an eSIM reseller platform, on the same stack we build for you. At most two active builds at a time, so the person who writes your code is the person you are emailing.

Book a 30-minute callAkaunting services
We reply within one business day. Turkish and English.

Before we argue, here is the evidence

Two things you can check without taking our word for it.

We have no client logos to show you and we are not going to invent any. What we do have is a product you can go and buy from, and a work history you can look up.

We run our own SaaS

Esimbit is ours — built here, operated here. A platform that lets eSIM resellers sell under their own name, on their own provider and Stripe accounts, in three languages. Its plans and prices are public at esimbit.com.
See the product

We know Akaunting from the inside

Our founder worked on the Akaunting team. That is a work history you can check, not a partner badge — and it is why we can tell you which licence tier you actually need before you build on it.
Akaunting services

Sound familiar?

If this is your week, you are in the right place.

These are the sentences people actually write when they come to us — from Akaunting forum threads, GitHub issues, and the first ten minutes of most discovery calls.

Running Akaunting

  • The installer stops at step 3 and the log is empty.
  • The one-click update died at 20% and now it says "Not able to download core".
  • The Cloud plan no longer fits, we want to self-host — but who maintains it?
  • We need e-Fatura, tevkifat and a running customer statement. We have no PHP developer.
  • Our hosting company has disabled proc_open.
  • We take backups, but invoice attachments do not come back on restore.

Running the business on spreadsheets

  • The whole operation lives in Excel and two people keep overwriting the same file.
  • Our process does not fit any packaged product we have tried.
  • A freelancer built it, disappeared, and never handed over the code.
  • We have the software. The one report we actually need does not exist in it.

What we do

Two things, done properly.

Both start with a small, fixed-price first step, so you find out what we are like to work with before committing to a project.

Akaunting: install, upgrade, extend

Independent services for self-hosted Akaunting. You buy and hold your own licence and App Store apps at list price — we sell labour and judgement, never resold licences.

  1. 1
    Health check5 business days

    A written report on your version, modules, hosting pre-flight, backups and licence-tier exposure, plus an upgrade plan. Credited against any follow-on work.

  2. 2
    Install or migrate3–5 days

    Correct PHP for both HTTP and CLI, TLS, cron proven by test-firing recurring invoices, SMTP with SPF/DKIM and a delivered test invoice, database and storage backups with a documented restore test.

  3. 3
    Upgrade & rescueFixed price per version jump

    Staged copy first, core before apps, snapshot and tested rollback, then a regression pass on the reports that genuinely break: profit & loss, tax summary, auto-numbering, recurring invoices, attachments.

  4. 4
    Modules & e-invoicingDiscovery, then fixed phases

    Built only on supported extension points — observers, view composers, jobs, permissions — so the next upgrade cannot delete your feature. Delivered as a private module in your own repo.

  5. 5
    Maintenance & supportMonthly, tiered by response time

    Monitoring, staged upgrades, verified backups with a quarterly live restore drill, and a monthly written report naming the version installed and what was checked.

See the Akaunting line

Tailor-made business software

Order tracking, field forms, stock, approval flows, reporting. When the process is the thing that makes you money, it should not be bent to fit a packaged product.

  1. 1
    DiscoveryPaid, fixed price

    We sit with the people who do the work, map the process as it actually runs, and write down the scope. You keep the document whether or not you continue with us.

  2. 2
    Prototype2–3 weeks

    A clickable, real-data version of the core flow, so the argument about what it should do happens before the expensive part.

  3. 3
    First releaseFixed price, weekly demos

    The narrowest version that replaces the spreadsheet, in production, with your data migrated and your team trained on it.

  4. 4
    MaintenanceRetainer or day rate

    Changes as the process changes, dependency and security updates, and someone who already knows the codebase when something breaks.

See how we build

How it runs

You always know what happens next and what you will be holding.

No proposal theatre, no discovery phase that quietly becomes the project.

  1. 01

    Discovery call

    30 min, free

    You describe the problem. We ask the awkward questions and say plainly whether this is work we should be doing.

  2. 02

    Written scope and a fixed quote

    Within 2 business days

    What is in, what is explicitly out, what it costs, how long it takes, and what you receive at the end.

  3. 03

    Short cycles with a weekly demo

    Every week

    Something running that you can click, every week. No status reports standing in for progress.

  4. 04

    Handover

    Before the invoice closes

    Repo access, documentation, a runbook, and a training call. Written so that the next developer does not need us.

What we build with

Backend & data
LaravelPHPNode.jsPostgreSQLMySQLRedis
Frontend
NuxtVueTypeScriptTailwind CSSLivewire
Platform & delivery
AWSDockerGitHub ActionsCloudflareLinux

Who does the work

There is a name attached to this.

Sevan Nerse

Sevan Nerse

Founder — Lokum Tech LLC

Remote · Turkish business hours

Laravel and Nuxt, with a stretch on the Akaunting team behind the accounting-software work: Senior Software Developer, 2018–2022. A work history, not a partner badge. Nobody here is an "official Akaunting partner", because no such programme exists.

I have also spent close to five years in HR technology, as Tech Lead and, in another period, CTO: recruiting, core HR, payroll and time tracking, performance.

Alongside client work I build and operate Esimbit, a SaaS platform that lets eSIM resellers sell under their own name. Running your own product teaches you what maintenance actually costs, which is the part most quotes leave out.

We use AI tools. Nothing ships without a senior developer reviewing it as carefully as they would review a colleague's pull request. The decisions, and the accountability, stay ours.

GitHubLinkedIn

Fit

We would rather lose the enquiry than the six months after it.

Here is where we are genuinely good, and where you should hire somebody else.

A good match

  • Laravel and PHP systems, including ones somebody else wrote
  • Akaunting installation, upgrades, modules and maintenance
  • Nuxt and Vue interfaces on top of an existing backend
  • Process software and internal tools replacing spreadsheets
  • Long-term maintenance where the same people stay on it

Not our cup of tea

  • WordPress theme work
  • Free mockups in exchange for a shot at the project
  • "Just implement the brief" with no room to question it
  • Work where the deciding factor is the lowest price
  • Projects that genuinely need a forty-person team
  • Multi-tenant Akaunting hosting — its licence does not allow it, and we will explain why

Ownership

Your code and your data, from day one.

This is the direct answer to the two fears we hear most: the developer who vanished, and the vendor you cannot leave.

  • A private repository you own, from the first commit
  • Running on your own server or your own cloud account
  • No licence you have to keep paying us for
  • Documentation and a runbook written for the next developer, not for us
  • A training call for your team before we step back
  • An exit document: how to deploy, where the secrets live, what to watch
See pricing and engagement models

Straight answers

The questions everybody asks on the first call.

Who owns the code and the data?
You do, from the first commit. Private repository in your account, running on your infrastructure. There is no licence fee to us and nothing you have to keep renewing to keep using what we built.
What happens if you stop working on it?
You get an exit document: deployment steps, where the secrets live, what to monitor, and the known rough edges. Plus a training call. We write the documentation for the developer who replaces us, which is the only test that matters.
Where is the data stored, and what about KVKK?
On infrastructure you choose and control, in the region you choose. We do not hold copies of production data beyond what a specific piece of work requires, and we say in writing what that is. The privacy page has the detail.
Lokum Tech LLC is a US entity — how does that work for invoicing a Turkish company?
It is a fair question and the answer belongs in writing, not in a sales call. We will state the invoicing entity, currency, VAT treatment and payment terms in the written quote before you commit to anything.
How quickly do you reply?
Within one business day to any enquiry. Maintenance clients get a stated response window by tier — a real window we will hit, not an aspiration.
Does self-hosting Akaunting instead of using Cloud actually make sense for us?
Sometimes yes, sometimes clearly not. It depends on your user count, your invoice volume, whether you need modules the Cloud plan does not carry, and who is going to maintain the server. The health check exists to answer exactly this, and we have told people to stay on Cloud.

Every good build starts with a conversation.

Tell us the process that hurts. We will tell you honestly whether we are the right studio for it — and if we are not, who is.

Book a 30-minute callWho does the work