Built for ourselves
We run our own company on CIRO NOISE. First our customers' requests arrived here, then came the wiki, the receipts and the meetings. Today other teams work with it too.
A back office in one place instead of eight tools
It all started with a support inbox that outgrew us.
With ciro.immo we run a platform for private landlords. As soon as it was live, the requests came in: by form, by email and later by SMS. Then came articles for the magazine, invoices from service providers and decisions from conversations among the four of us. Every topic sat in a different tool with its own login and its own roles, and whoever was looking for something first had to find the right tool. So we built the workspace we would have liked to buy: one inbox for requests, a wiki for our docs, boards for the tasks, receipts with cost centers and an AI that has read all of it.
CIRO has run on CIRO NOISE ever since. Every landlord's request lands here, we book every expense here, we plan our magazine on a board, and whoever joins reads their way in through the wiki. From day one we were the product's strictest customer. We changed what got in our way and cut what nobody used. Once everything ran reliably, we opened CIRO NOISE to other teams. They work in the same workspace as we do, each team in its own organization.
Three rules we build CIRO NOISE by
Every new feature has to fit these three rules, or we don't build it.
One permission system for everything
You decide once who may see what, with role bundles per feature. Wiki, boards, support, accounting, passwords and the AI all follow that one decision. When someone leaves, you remove them in one place, and on every single access CIRO NOISE checks that nobody sees another organization’s data.
EU and verifiable
Servers and AI models run in EU regions we can name. Every answer from the AI cites its source, every wiki change is kept as a version, and every receipt shows who recorded it and when. That way you can check everything yourself.
Fewer tools for your team
A new feature is added only when it replaces another tool and works with the other features. That's why there are no Gantt charts, and custom fields are limited to five per board. In return, a process runs in one piece from the request to the report.
Two founders, two disciplines, one back office
Engineering and processes sit at one table. Both of us use CIRO NOISE every day for our own work and are the first to notice when something is missing.
André Teich
CTO & Co-Founder
LinkedInPrincipal Engineer at one of Germany's largest e-commerce companies, responsible for the architecture of a platform that serves millions of customers across Europe every day. Before that, 20 years of software development in consulting, agency and corporate roles, with projects for many large DAX companies. His standard has always been the same: think a system through from start to finish before the first line is written, and put the needs of the person at the screen above the elegance of the solution. That thoroughness has been in CIRO NOISE since the first feature.
André builds the foundation the features stand on. Part of it is the separation between organizations: every access to data is bound to its own organization. Another part is the permission system of three tiers and role bundles that all features share. An automated test in the code fails as soon as any record is read or changed without that boundary. The opening to the outside is his as well: through an open standard, AI tools such as Claude work with boards, wiki and customer records, and through an API your own scripts can do the same. They have exactly the permissions of the person who created the access. If that person belongs to several organizations, the system asks instead of guessing.
Markus Froese
CEO & Co-Founder
LinkedInManagement consultant focused on turnaround, restructuring and post-merger integration. For years his daily work was helping corporations simplify complex processes, rebuild structures and clarify responsibilities so that work flows again. Whoever merges two companies is the first to see what happens when every department brings its own tool, its own filing and its own role model. The tools of small teams have the same problem, just without the department that cleans it up.
Markus leads CIRO and asks of every proposal first which step it removes. The view of the process is his: a request becomes a task, the task becomes a receipt and the receipt becomes a report, and nobody copies anything. So is the role model taken from everyday work, with named bundles like Project work, Customer service and Management instead of checkbox lists per person. His yardstick for every feature: a good tool gets better when the unnecessary disappears.
The team behind it
CIRO GmbH, Eching near Munich. We build two products on one foundation: ciro.immo for private landlords and CIRO NOISE for teams that want to run their tasks, customers and finances in one place. Both run on servers in the EU and follow the same rules for permissions and data protection. And we run both with the back office you see here.
Work with what we work with
The first two seats are free, all features included, no credit card. We answer your questions personally.