Project management that shows where work piles up.

As of October 2026: none yet. KlangCity is in Early Access, and Klangfeld has been running its own business with it since July 2026. The first three organisations become Early Access partners.

Not yet. That is exactly what the partner programme is for: three organisations, 40% off Pro or Business for 12 months, in return for being named and one reference call.

Not yet, because there are no paying customers yet. Reference calls come from the partner programme. Until then we show you KlangCity and its permissions live in a session.

KlangCity is developed and operated by Mittu Klangfeld UG (haftungsbeschränkt) in Cologne, Germany, registered at the Cologne local court under HRB 129013. Self-funded. The team is one person: development, support and data protection in one pair of hands. That is why our exit commitment applies, with 6 months’ notice if we shut down and export at any time (terms, section 12.4).

The product is ready for everyday use. Stable: tasks and Kanban, the city, chat, calendar, file storage, video calls, weekly report and export. In Early Access: meeting minutes, email inboxes, inventory and material planning, incoming invoices and the apps for iPhone and Android. See the maturity map.

The /api/v1 interface and the export format stay backward compatible for 24 months, and we announce significant changes 30 days in advance (terms, section 5.6). The target for calendar sync is the end of 2026, for single sign-on Q1 2027. The Android app has been on Google Play since October 2026. Private projects come first: if time gets tight, the others move back, and we say so in good time. Microsoft 365 and ERP on request.

The dedicated instance is available as an add-on on request, for Business: its own server in Germany with its own database, its own storage bucket and its own encrypted backups. Same code, separate keys, operated by us. The concept is in the review pack, and the price depends on the effort.

App, video calls and speech recognition: our own server at Hostinger in Frankfurt am Main. Uploaded files and backups: Hetzner in Falkenstein. Backups are encrypted, kept 14 days locally and 90 days externally.

We handle payments through Stripe Payments Europe in Ireland under our own responsibility. Stripe therefore does not process any data on behalf of your organisation.

Audio is only processed in the memory of our server in Frankfurt and never stored. Transcription only happens with consent: the switch in the call is off by default, and whoever switches it on agrees. Under Apps, Security the organisation can switch off transcripts entirely. After the minutes are written, the raw transcript is deleted. All members can read minutes, in closed groups only their members, guests never. For new organisations they are deleted 30 days after the meeting, and your organisation can extend or remove that period.

Internal security reviews of code, servers and legal texts, most recently in September 2026, with AI-assisted code analysis. The review log with scope, method and results is available on request in the review pack.

Every night the database and files are backed up, encrypted at Hetzner. Maximum data loss is 24 hours, and a watchdog raises the alarm if a backup is older than 30 hours. Recovery time is estimated at 4 to 8 hours, not yet measured, with a target of 8 hours in the data processing agreement. Restore tests on 6, 24 and 26 September 2026, most recently from the encrypted external copy; the logs are in the review pack.

For the weekly report: first names, task titles, key figures and signals. For signal explanations: only the signal, person, group or project. Plus meeting transcripts, the title and description of new tasks for classification, your questions to Klangi and, for orders, the wishes without contact details. No audio, and files only as design images in material planning. The full list is under AI with cards on the table.

No. This is set out in our terms (section 13.5), in the data processing agreement (clause 1 and Annex 3) and in Anthropic’s terms for API customers.

In the Business plan: 99.0% availability, measured during service hours, Monday to Friday from 8 a.m. to 6 p.m. German time. We respond to incident reports within 4 hours during that time, otherwise from the start of the next service period. The platform is monitored around the clock and restarts itself for the most common errors. Credit of 10% for each started 0.5 percentage points below target, at most one monthly fee. Announced maintenance of up to 4 hours a month and outages of the AI provider don’t count (terms, sections 5.5 and 13.7).

Yes. The owner downloads the whole organisation as a ZIP file: all areas as JSON and all files with names and folders, up to 8 GB. Each person also gets their personal export under Articles 15 and 20 GDPR, which is the only place direct messages appear. A sample export of the demo organisation is in the review pack.

Monthly plans: at any time, effective at the end of the month. Yearly plans: 12 months, cancel up to 30 days before the end, otherwise the contract renews for 12 months (terms, section 12.2). Export works at any time and until 30 days after the contract ends. Data disappears from backups after 90 days at the latest.

If we shut down, at least 6 months’ notice. If the company is sold, a special right to cancel with a pro-rata refund. Plus export at any time and until 30 days after the contract ends (terms, section 12.4).

Roles: owner, admin, member, guest. For confidential matters there are closed groups: admins or the group lead close a group, and then only its members see the group channels and the minutes of their group calls. They protect against colleagues, not against the owner; if the owner adds themselves, the group sees it. Only the people involved see direct messages, and guests can only read. Private projects are planned for Q4 2026 and have top priority on the roadmap; until then projects, tasks, file storage and calendar are visible to the whole organisation. Two-factor can be made mandatory, access can be restricted to specific networks, and a log shows all irreversible actions and every access via the support function.

The owner chooses one of five levels: all members, person and leads, the person with numbers per group for leads, only the person, or off. New organisations start with “Person and leads”. The team view prevents KlangCity from flagging individual people. Tasks with priority and assignee stay visible to everyone until private projects arrive. Guests never see signals about people. The owner decides with a separate switch whether the AI may write anything about the wellbeing or behaviour of individuals in the weekly report; it is off by default. The purpose limitation is set out in Annex 4 of the data processing agreement: taking pressure off people and sharing out work, no monitoring of performance or behaviour. Try it out or ask us to show you live.