A sovereign online workplace
Stop renting your digital office.
Run it on infrastructure you control.
You do not have to choose between modern collaboration and control.
Hosted where you choose, or deployed on infrastructure you control.
Problems we help solve
The work is modern. The workplace should still be yours.
The same practical problems show up from small teams to large organisations. Control, leaving, reliance on one supplier, and work spread across too many places.
-
You do not fully control the data
Where it sits, who administers it and who can reach it should be your decision — hosting, access, backup and retention included.
-
Leaving is a project
Files, identity, documents and talk on one rented platform are not a folder you can pick up. Leaving is an export and a cut-over.
-
One supplier holds too much
Pricing, features and continuity sit with another provider. A workplace you own reduces that reliance.
-
Work is scattered
Files live in email, laptops, shared drives, chat and personal accounts. Sharing and collaboration belong in one company-controlled place.
-
Headcount multiplies licences
The cost model moves away from per-user seats toward infrastructure, operation and support. See the questions for what that does not promise.
-
Work should stay with the business
Personal tools and departing accounts leave holes. Company-managed accounts keep the files with the organisation.
There is another model: a workplace you own, on infrastructure you control. Nextcloud is how that workplace is built. OSOS designs, deploys, integrates and can operate it. What that control covers.
-
01
We build it
We build it around how your organisation works: Community Nextcloud, deployed on infrastructure you choose.
-
02
You own it
Credentials handed over. You keep the keys. The workplace sits where you want it.
-
03
We can operate & support it
Optional managed support: administration, updates, monitoring and incidents — priced on its own.
Practical sovereignty
Control, in the things that matter.
Ownership here means the workplace, the data and the keys stay with you.
-
Hosting
Hosted where you choose, or deployed on infrastructure you control.
-
Administration
Your team administers it, or OSOS does if you ask.
-
Keys
Credentials are handed over. You keep the keys that apply to the workplace.
-
Data
Files stay where you put the workplace. OSOS does not take them home.
-
Backups
Backup and restore stay a business decision, not only a supplier setting.
-
Portability
Move host, or take the stack in-house.
-
Replace OSOS
After handover you can run it without us, or appoint someone else.
We work on what we build
OSOS runs on the same model.
This is not a copy of the stack every customer receives. OSOS runs its own business services on the same principles: open software, a workplace we control, and the keys in our hands.
-
Updates
The workplace we use is kept on a maintained release, not left at the version from the day it was installed.
-
Backups
Files and the service itself are backed up, and a restore is part of the operating routine.
-
Monitoring
We watch the service we depend on, not only the one we hand over.
-
Security
Access, patching and the exposed surface are treated as operating work, not a one-off install step.
-
Recovery
When something fails, the path back is known before it is needed.
The workplace
Everyday work, without renting someone else’s digital office.
Community Nextcloud is the collaboration core we use to deliver that ownership. It scales from small teams to large organisations by changing the infrastructure behind it — not by changing the product. A small team pulling files out of inboxes, a department that wants chat next to the documents, or a larger organisation that wants the service on its own infrastructure: same workplace, different scale.
-
Chat and calls
Conversation next to the files it is about.
-
Mail and the diary
Mail beside the calendar. A mail server is stood up only when the case needs one.
-
Shared files
Shared folders and older versions, in one place.
-
Documents together
Edit documents in the workplace. You choose the office option. The files stay here.
-
Search the work
Search inside documents, including scans.
-
Contacts and passwords
Contacts, shared passwords and bookmarks on the same workplace.
-
Your own mark
Your logo on the login and the workspace.
Why sovereign
Your infrastructure vs rented productivity suites.
If you already use Microsoft 365 or Google Workspace, the difference is who owns the workplace — not a longer feature list. What that control covers is set out above.
| Question | This workplace | Microsoft 365 / Google Workspace |
|---|---|---|
| Ownership | Customer-owned instance. Keys handed over. | Seats rented in a vendor suite. |
| Data control | Customer-selected location. Files stay there. | Vendor-controlled cloud and terms. |
| Licensing | Free software. You pay for the work. | Recurring per-user product licences. |
| Portability | Move host or take the stack in-house. | Leaving means an export and cut-over. |
| Support | Independently contracted support, if you want it. | Support provided within the vendor/subscription model. |
| Administration | You administer it, or we do if asked. | Admin consoles inside their platform. |
Replacing a rented suite does not mean replacing every workload with one product. See how an open workplace maps workload by workload.
How we help
We build it. Running is a separate choice.
A specialist consultancy — not a large MSP in miniature. The build is billed once. Running is priced separately, and only if you ask. No ready-made packages.
Operating model
-
01
Automated, repeatable deployments
The same build path, shaped to how your organisation works.
-
02
Controlled upgrades
Planned changes rather than surprise weekends.
-
03
Customer ownership
After the build, your team can administer it, or we can.
-
04
Your infrastructure or hosted for you
You choose the country and provider if we host. Backup and recovery stay a business decision, not only a vendor retention setting.
The path
-
1
Assess
What moves, what stays, and who will run it day to day.
-
2
Build
Community Nextcloud, TLS, agreed apps, branding. Deployed on infrastructure you control, or hosted for you. Credentials are handed over at the end of the build.
-
3
Migrate and train
Files first, mail if you want it. Training is scoped and priced with the case. It is not included by default.
-
4
Operate
Optional. Administration, updates, monitoring and incidents, priced on its own. Hours and response targets belong in the contract. You can run it yourselves after handover.
Always in the build
- Community Nextcloud Hub, installed and configured.
- TLS and a sound baseline.
- Agreed apps for files, talk, mail, calendar, documents, contacts, passwords and bookmarks.
- Credentials handed over.
- Your mark on the instance.
Never inside the install fee
- A product licence. The fee is the work.
- A purpose-built application. Shaping standard apps is in scope.
- Ongoing support after go-live. That is optional.
Scope on that path
Training sits in Migrate and train, priced with the case. Operate stays optional. Credentials are handed over in the build.
Pricing
How a figure is reached
After a short note we come back with a shape and a figure. What moves the number: deployment, hosting, migration, integration, training, optional support, and the brief itself.
Questions
In brief.
Is this a licence we buy from you?
No. Community Nextcloud is free software. The fee is the work of building it, shaping it, hosting it if you ask, and supporting it if you ask.
Is a lower bill guaranteed?
No. The cost model moves away from per-user seats toward infrastructure, operation and support. It is not an automatic saving.
What does a first conversation need?
A name, a way to write back, the organisation, roughly how many people would use it, and a few words about the project.
Do you train the team?
Training is available. It is scoped and priced with the case, not included in the install fee. How much belongs in the quote depends on who will run it day to day.
Can it replace the suite we use today?
Nextcloud is the collaboration core — files, talk, calendar, contacts, and a mail client. Document editing uses a supported office platform. A mail server, identity and some project or knowledge tools often sit beside it. Selected existing services can remain. See the workload map.
Who looks after upgrades, backups and downtime?
If you run it yourselves, those jobs stay with you. If you take optional managed support, OSOS handles the upgrade path and backup checks agreed in the case. Downtime is not promised at zero.
Can you bring the old work across?
Yes. Files first, mail if you want it. What stays is part of the assessment.
How large a team?
From small teams to large organisations. Scale means changing the infrastructure behind it — not a different product, and not a claim about prior OSOS customer scale.
Contact
Want to see whether this fits your organisation?
Send an enquiry below, or download the 2-page overview.