Romy / About

IT operations from Munich, for mid-sized companies.

For anyone who wants to know who is behind Romy before letting a Microsoft app in. This page says who we are, what Romy is built for and where it runs.

§ 01Who we are

Built from everyday IT work.

Romy GmbH

Munich, founded by Falk Sonnenschmidt

We come from IT operations: identity, devices, licences, compliance. Romy is the tool we wished for as overloaded admins.

Who it is for

IT teams at companies with 100 to 350 employees

These teams are usually too small for what they carry. Romy takes the repetition off them and says plainly what it cannot do.

§ 02Stance

What Romy does, and what it never does.

Read

Read first

Romy reads device state, licences and access and proposes, with reasons, what to do.

Confirm

Act after confirmation

An action runs only once a person confirms it. The confirmation is valid for 15 minutes and once.

Never

Dangerous actions stay out of reach

Romy cannot trigger a device wipe, a device retire, a passcode reset or a user deletion.

You don't work in IT. You are responsible for it. That is what Romy is built for.

§ 03Operations

Where Romy runs and what is kept.

What you should know before you consent, in five lines.

Hosting
Azure Germany West Central (Frankfurt)
Data
Romy keeps no copy of your data: fetch, prepare, return.
Log
Kept: who queried what and what was triggered, without content.
Revoke
Each Romy app can be removed on its own in Entra ID.
Evidence
No certification (ISO 27001, SOC 2). We send a data processing agreement (DPA) on request.

Security and data in detail →

Get to know Romy.

Set Romy up yourself, read-only and in three Microsoft dialogs. On request, sales walks you through the three steps. You click in your own Microsoft 365, and we explain each step.