Updates
Not a technical changelog, just updates on showcases, releases and learnings from building Kumiko.
Subscribe to updates via RSS →
Build your own app. The docs and the Show Pony tutorial take you from the first command to a running application.
Read the docs →The new helpdesk feature takes questions, contact requests and problem reports from the website and from inside the app. The app's SystemAdmins get a mail without personal data and answer from an inbox of their own.
Apps declare which events leave the system as webhooks, and personal access token scopes release them. kumiko api-docs writes the HTTP API reference and an OpenAPI 3.1 file from the same registry, and fails in CI when the docs fall behind the code.
The opt-in feature tenant-inactivity mails the owners of an unused account before a deadline, for example 30 and 7 days ahead, and then files the regular deletion request with its waiting period. Data under a retention period stays until that period ends.
Postgres now enforces tenant isolation in every Kumiko app by default. A query without a tenant context sees no tenant rows, and an app with an unprotected tenant table does not start. All our own apps have run on it in production since today.
Every list in a Kumiko app can give its users a view menu for columns and density, pinned columns, groups with sums from the server, actions on a selection and an Excel export. Each part is one key in the screen definition.
Every mail and PDF in a Kumiko app comes from a template in the database. Admins change text, logo, layout and attachments in the browser, check the result with sample values and publish it without a deploy.
PublicStatus now runs on publicstatus.eu with a new design, uptime charts built from hourly and daily buckets, down and recovery alerts in Slack, Discord, Teams and Telegram, and consumer protection for paid plans.
Attach a PDF, image, CSV, text or Word file to a conversation and the Assistant reads it with your question. Uploads are checked by their content, and attachments leave with the account.
Our apps no longer read their keys as plaintext from the pod environment. They unwrap them at boot from Scaleway Key Manager in Paris, so the data and the keys that open it have different custodians.
A factual look at the current Offlot repository: 3 AI steps, 21 app-owned features, 147 test files and 54 integration tests.
Offlot is now a first-class Kumiko showcase: three AI pipeline steps connected to vehicles, campaigns, a calendar, public vehicle pages and leads.
Talk to your app: open, search, count, change. With approval per action the way Claude Code does it: every write is proposed as a card that a human answers.
Kumiko is not a toolkit you first need to master. You bring the workflow, and we build the software around it.
TOTP-based 2FA for every Kumiko app: QR enrollment, recovery codes, and a login-time challenge that revokes other sessions on change. Bundled feature, no custom code.
Show Pony is a complete open-source RSVP app with a step-by-step tutorial. Read the source, follow the chapters and ship a real multi-tenant SaaS on Kumiko.
The CashColt showcase page now uses Playwright screenshots from the live app: dashboard, calculator, property folders. No demo mockups.
The PublicStatus showcase page shows real screenshots: status page, uptime monitor, custom domain, white-label branding, all from the live app.
Monitoring, CI, and Alertmanager can open incidents, flip components, and schedule maintenance, via personal access token with no browser login. Team plan+, docs live.
We're taking on pilot customers: joint setup sprint, 3 months of guidance, honest case study with veto rights. Places on request. For teams with a concrete internal use case.
Three questions show up in almost every pilot conversation: hosting, audit, lock-in. How we answer, and why it's not marketing fluff.
cashcolt.kumiko.rocks is in production: signup, profile and logout. Bilingual de/en with real legal pages. A showcase app we operate ourselves.
Users manage password and email, delete their account with a full GDPR chain, plus Art. 15 access for email subscribers. Compliance without a support ticket.
Status pages aren't one-size-fits-all: tenants define custom fields on components and incidents, visible in HTML and RSS with no code deploy.