LONGTOM
You write software. Somewhere behind that there is a company to register, a return to file, a receipt to book and a customer waiting on a reply — and none of it is why you started. Longtom is a small daemon that runs on your own machine and does that half of the job.
Not released yet Longtom is in development. This page describes what it is; there is nothing to download today.
Which form to trade as, which registrations, in which order, and which one blocks which. It is done once and then it is finished — so the value is in getting the sequence right the first time rather than in a dashboard you keep coming back to.
Longtom holds the answers for your country rather than asking a model to guess at them: the thresholds, the deadlines, the authority that issues what, and how long each step usually leaves you waiting.
A universal cashbook. Bank statements in, receipts read out of your mail, rules learned from how you categorise, a trial balance out, and the periodic return prepared in the authority's own labels with every line traced back to a ledger row.
It prepares filings. It never lodges one — a filing is a statement about something a person did, under their identity, at a government portal.
The part that lasts longest and the part built to go straight to the AI. A customer writes in; the message is classified, deduped, attached to whoever sent it, reproduced against your repository, and a fix is prepared as a branch with a reply drafted beside it.
The patch lands in a temporary git worktree. Your own checkout is never touched, and the work always stops at a branch, because merging belongs to whoever is working in it.
Longtom bundles no model and sells you no tokens. It detects the coding CLI already installed on your machine — Claude Code, Codex, Cursor, Antigravity, Gemini, OpenCode, Aider, or a command you name yourself — and hands it work with the evidence already assembled.
A fact researched once and shipped as data costs one piece of research. The same fact left for a model to derive costs it again for every user, every time — the same tokens, the same electricity, the same wait, and a slightly different answer each go. So the rates, the deadlines, the fees and the order of the steps are compiled into the program, each with the date it was last confirmed against a primary source.
The model is for what genuinely needs one: reading a pile of documents, reconciling a bank feed, drafting a reply, working out whether a rule moved.
One folder holds everything: the database, the documents, the backups. Secrets live in a separate encrypted vault that the database never sees, so an exported database carries no credentials by construction. There is no account to create and no server keeping your books.
Zero runtime dependencies — not a small number, none. The supply-chain surface of a program holding your payment keys and your customer mail is worth being unreasonable about.
Listing a nation is a claim: what the consumption tax is called and its rate, the registration threshold, what the return is called, its cadence and its real due dates, which authority issues what, what a business there is expected to be registered for, and what its privacy law and regulator are. Anything less is not offered. A plausible rate with an invented due date is worse than an honest "not yet".
Where no tax is named the answer is not missing. The country either levies none at all, levies it state by state, or is part-way through replacing one system with another — and the profile says which, in a paragraph, because two words would get it wrong.
The ones not here are a to-do list, not a verdict on a nation. Only two things keep a country out for good: a tax-and-company system so different in shape that the model Longtom is built around would not describe what a business there actually does, and a country under sanction.
Country data updates on its own, separately from the program. A rate that moves does not wait for a new version — a signed pack is checked against a key compiled into the binary and put in force, and anything you have confirmed for yourself still outranks it.
Longtom is for a business of one — one coder, possibly one support person, no employees. That is not a stage on the way to something bigger; it is the whole product. An employee is roughly the point at which somebody should be leaving, and building toward that would make this worse for everybody who is not there.
Outgrow it and you go to your country's usual accounting package. The ledger exports OFX for exactly that reason, and each country profile names the packages an accountant there will actually accept. The records pack is one zip an accountant or a tax office can read: the ledger, the trial balance, every prepared return, the invoice behind each payment, and a covering letter explaining how the figures were arrived at.
None of that is a recommendation to go. It is the door being unlocked from the inside.
Longtom is being built in the open by one person, for people in the same position. When there is something to install, the way to get it will be here.