zaflache
292
Recorded changes to the database layout
137
Database tables
392
Permission rules kept in the database itself
54
Server-side functions
12
Functions that check what people post
2
Phone systems served by one set of code
Proof: two systems we run ourselves
1 item
Our own systems, open to inspection
Two working systems of the company. For each one the same: what runs today, what is still being built, when we last checked it was up, and a separate page describing in detail what sits under the hood.
01
Two systems of our own
No drawings of screens here. Both systems below are publicly live, we look after them ourselves, and we state their status as of the day you are reading this page.
0101
Two systems we maintain ourselves
01022 systems · status as of the day you read this
Left and right arrow keys switch the item shown on the stage.
Item 1 of 2: zaflache
zaflache
A classifieds portal for a city: listings, companies and services in one place, with a phone app on its way to the stores.
technical detailsFufuTool
One listing, one screen, many portals. Today it publishes to zaflache, Allegro and OLX; Otomoto is still in progress.
technical detailsNumbers from the code of each systemcounted 2026-09-03
FufuTool
97
Recorded changes to the database layout
68
Database tables
101
Permission rules kept in the database itself
2,010
Test cases
222
Test files
15
Kinds of job the system runs in the background
9
Tools for connecting to ChatGPT and Claude
TogetherThe two systems talk to each other through the public zaflache connection for partners (the technical name: an API). We wrote down what that connection promises, as if dealing with an outside company, because that is how we do it with clients.
A classifieds portal for a city: listings, companies and services in one place, with a phone app on its way to the stores.
A local classifieds portal: listings, property, services, rides and company profiles, with posts checked before they appear and a phone app.
Technologies: React · TypeScript · Vite · Supabase (PostgreSQL) · Capacitor · Tailwind
Status
Live
- Accounts with roles from ordinary user to administrator; who may see what is decided by the database itself, not by the screen.
- Company profiles with tax-number verification against the official VAT register, a team and a publishing calendar.
- Content moderation in three layers, with a reason given for every decision, an appeal path under the Digital Services Act, and labelling of AI-generated content.
- An AI assistant that helps write a listing, suggests a price, drafts a listing from photos and takes listings in from a spreadsheet file.
- A public connection for partners: they sign in without ever seeing a password, and every notification we send them is signed. FufuTool uses it.
- Listings show up in Google even though the portal works like one single app: every subpage has its own address and its own description.
In progress
- Android and iPhone apps in the stores.
- Card payments with real money.
Numbers
status as of 2026-09-03| What we count | How many |
|---|---|
| Recorded changes to the database layout | 292 |
| Database tables | 137 |
| Permission rules kept in the database itself | 392 |
| Server-side functions | 54 |
| Functions that check what people post | 12 |
| Phone systems served by one set of code | 2 |
One listing, one screen, many portals. Today it publishes to zaflache, Allegro and OLX; Otomoto is still in progress.
A screen for sellers that catches missing details before publishing, sends the listing out to the portals, and tries again when a portal does not answer.
Technologies: Next.js · React · TypeScript · Supabase (PostgreSQL) · Stripe · Tailwind
Status
Live
- A listing wizard with a list of what is missing before publication.
- Import of existing listings instead of retyping them by hand.
- Editing with an "Undo" window after saving.
- Jobs done in the background one after another, tried again after a failure, with three layers of protection against a duplicate (on Allegro a duplicate is a paid listing).
- Publishing to zaflache through the partner connection, and to Allegro.
- Publishing to OLX — the third live portal next to zaflache and Allegro.
- Stripe payments taking real money.
- "When... then..." rules, rehearsed before you switch them on.
- Price autopilot following rules set by the seller.
- Reusable listing templates.
- Photo drop from a phone via QR code.
- A team split into separate work areas, each with its own permissions.
- A connection to ChatGPT and Claude: draft a listing from a conversation, check whether it is ready, check whether it went out.
- A separate part for companies that build flats for sale, meeting their legal duty to publish prices, with the daily file dane.gov.pl expects.
- Daily backups; on 29 August 2026 we loaded one back to prove it works.
- A public status page: status.fufutool.pl.
In progress
- Otomoto (dependent on a partner agreement).
- InPost labels (the real access keys are not set yet).
Numbers
status as of 2026-09-03| What we count | How many |
|---|---|
| Recorded changes to the database layout | 97 |
| Database tables | 68 |
| Permission rules kept in the database itself | 101 |
| Test cases | 2,010 |
| Test files | 222 |
| Kinds of job the system runs in the background | 15 |
| Tools for connecting to ChatGPT and Claude | 9 |