# 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.

- Page: https://www.ciro-noise.de/ueber-uns
- Deutsche Fassung: https://www.ciro-noise.de/ueber-uns.md

## 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

### Markus Froese, CEO & Co-Founder

## 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.

## CIRO NOISE at a glance

- CIRO NOISE is a workspace for small businesses and teams of up to about 50 people: wiki, tasks, customer requests, finance with quotes and invoices, customers (CRM), meetings, knowledge with AI, social media, password vault, and time tracking behind one login.
- Price: the first 2 seats are free, with every feature. Each additional seat costs €25 per month plus VAT. No credit card to start.
- Privacy: servers and AI run in EU data centers, content never trains AI models, and permissions apply per person and feature.
- AI connection: Claude and other AI assistants connect through MCP, the open standard for AI tools, with exactly the permissions of the person.
- Provider: CIRO GmbH, Eching, Germany. Contact: hello@ciro.gmbh, phone +49 89 24 88 31 22.