Encrypted file transfer, document tooling, storage hygiene — and a private AI platform when you want one. Every product is engineered to deploy inside your network and never reach beyond it. Built in Europe, for organizations that cannot hand their data to someone else.
Start where you are.
People land here for one of three reasons. The first one asks nothing of you: no account, no card, no call.
Take something today.
Privatta and the markdown editor have builds up right now. The rest go live the moment each installer finishes. Beta builds are the whole product, not a stripped demo with the good parts locked.
- PrivattaWindows · Linux · Android
- Markdown Reader & EditorWindows · no subscription
- WebRTC Relay ServerOpen source · self-hosted
Put it in front of your people.
Per-seat pricing, published, with no sales gate in front of it. Want to pilot it first? We help you install and configure it inside your own environment.
Read it before you run it.
Architecture papers, the governance model, and the source of the parts that are open. Written for the person who has to sign off.
Different jobs. One rule: nothing leaves your building.
Encrypted file transfer, offline document tooling, storage analytics, a private AI platform, and the open-source plumbing underneath it. Each one stands on its own, so you do not have to adopt a suite to get value out of a Tuesday. Start with whichever one solves the problem in front of you.
A small company in Kragujevac, Serbia.
Royal Softworks is privately owned and paid for by the people who buy the software. That is the whole business model, and it is why the products run on your hardware instead of ours. When you write to us, the reply comes from someone who wrote the code.
Kragujevac, Serbia. Built, supported and answered from Europe, in one time zone, by the same people every time.
We do. Self-funded since 2024, so the only people we answer to are the ones paying for the software. No venture capital, no board asking us to find new things to do with your data.
Close to nothing. The free products never ask who you are, and none of them phone home: no telemetry, no analytics baked into the build. A Pro licence does come with an account, since somebody has to own the subscription and the seats, but it lives on this website rather than inside the software.
The architecture, in enough detail for a security review: retrieval, sandboxing, the governance plane, and the source of the parts that are open. Read it before you ever run an installer.
Customer logos, and we will not invent them. We are young. Everything we claim is something your own security team can test on your own hardware, which is the only proof worth having anyway.
Write to a person.
Not a routing layer, not a chatbot, not a form that disappears. Same day where we can, one business day at the outside.
More about how we are fundedThe work people bring us, field by field.
Ten jobs, written the way the people doing them describe them. Find the one that sounds like your week.
A litigation partner needs to search, summarise and draft against privileged material, with no copy of it existing anywhere outside the firm.
A practice manager needs records searchable and summarised at the desk they were written on, because patient data leaving the building is a reportable event.
A finance director at a regulated lender needs client books and models analysed in-house, under the firm's own retention and audit policy rather than a processor's.
A systems officer needs software that installs on an air-gapped network and keeps working there for years without ever calling home.
A project lead on site needs 40 GB of drawings in the studio's hands tonight, without a file-sharing account or a download link that outlives the project.
A principal investigator needs to question a corpus the licence forbids uploading, and keep unpublished results off third-party infrastructure.
A post supervisor needs rushes moved between edit bays at line speed, and duplicate masters found before the storage bill doubles again.
An MSP engineer needs a client's servers audited over SFTP and a cleanup plan handed back. No agent installed, no cloud account opened.
A venue owner needs guests to scan a code and get today's menu (priced, live and theirs) instead of a PDF and an app install.
A platform engineer needs a signalling relay small enough to read end to end and host in-house, so their users' peers never meet on someone else's server.
User stories, not customer quotes. Case studies go up when we have real ones.
Your field is not on the list? Describe itThe business case for keeping your data inside your building.
Not a privacy stance for its own sake. For anyone who already owns the hardware it is the cheaper, calmer and more defensible way to work. Three parts, so you can take it to whoever signs.
Your data stays on your hardware. By architecture, not by configuration.
Inference, indexing, embeddings and storage all run inside your network perimeter. No outbound calls to a vendor model, no telemetry pipe you forgot to disable. Install it on an air-gapped machine and it keeps working there indefinitely.
Frameworks aligned at the design level, not bolted on afterwards.
Data residency and access control are properties of the stack. Audit trails are built in. The legal review for an on-premise install is usually smaller than for a cloud evaluation, because there is less surface to assess.
- GDPR
- ISO 27001
- HIPAA
- SOC 2
- NIS2
Your Tuesday does not stop because a provider is having a bad day.
Local products keep running through a vendor outage, a regional incident, or a contract renegotiation you did not ask for. The software runs on hardware you already own, and no one else holds a kill switch.
Every arrow points inward. There is no route out of the diagram, because there is no route out of the architecture.
Predictable pricing
Clear per-seat pricing. No usage-based cloud fees that scale with how much work your team gets done.
Your IP stays your IP
Internal documents, proprietary methods and client data are never used to train anyone else's model.
Hours back in the day
Less time hunting for the right file, less time reformatting the same document twice.
Four kinds of team. Four reasons to keep it in-house.
Pick the one closest to you. The software is the same in every case; what changes is which part of it you will care about on the first day.
Protect IP. Reduce compliance overhead. Accelerate decisions.
Enterprise teams handle sensitive internal knowledge daily: strategy documents, contracts, financial models. We give your organisation the tooling to work on it inside your own network perimeter: secure exchange, document search, and AI where you want it, with governance built in.
- AI assistant trained on internal documents
- Secure file exchange across departments and partners
- Sub-second classification and retrieval
- Centralised access control and audit logs
Experiments from the same workshop. Not part of the suite.
Live QR menus for venues and an AI try-on app. We built them because we wanted them to exist, and you are welcome to use them. Same engineers, same privacy instincts, no enterprise pitch attached.
Questions worth asking before you install anything.
The ones we get most often are answered in plain language. If yours is not there, just ask us.
All 20 questionsTalk to the team that actually builds the software.
Pilots, licensing, demos, security questionnaires, or a question you are not sure is a question yet. All of it lands with engineers and product leads rather than a routing layer, and none of it starts a drip campaign.
Send us a message
Tell us what you are trying to do. A person reads it and replies within one business day.