Projects
Projects that went into production.
How well a system is built shows in how long it keeps running.
| System | In service | ||
|---|---|---|---|
| Bio pages and short linksProductStart | 26monthsongoing | ||
| Payment links and workspacesPlatformStart | 10monthsongoing | ||
| Content recognitionProductStart | 9monthsongoing | ||
| Multi-tenant PaaSPlatform · endedStart | 16months | ||
| Licences in one placePlatform · endedStart | 10months | ||
| Receipts filed automaticallyAutomationStart | 1monthongoing |
A selection: the most recently built systems. More than thirty have been built over the last few years, and older ones are still running.
The problem behind each system.
The full description, the technology and the figures live on that system’s own page.
Product
since · 2 years
Bio pages and short links
One landing page per person, editable in minutes, with short links and click counts behind it.
Platform
since · 10 months
Payment links and workspaces
Create payment links, keep teams separate and account for every payout — without building a billing system.
Product
since · 9 months
Content recognition
Finds where your content resurfaces online, including where it has been cropped, slowed down or re-uploaded.
Platform
– · 16 months
Multi-tenant PaaS
One codebase, many tenants — each with its own database, its own network and its own backups.
Platform
– · 10 months
Licences in one place
Who holds which licence, when it starts and when it runs out — in one place, across every tenant.
Automation
since · 1 month
Receipts filed automatically
The system collects the receipts for the month itself: it reads the mailbox, checks the sender and files the receipt.
Next step
We compare your plan with one of these projects.
Describe the system you have in mind. We will name the project on this list that comes closest to it, and the place where it got expensive.