Cloud services
Your cloud services. A local way forward.
Email and shared files are where a great deal of business happens. They are the starting point for a practical local continuation environment.
We map the services you use, the data you need and the work you must keep doing. Each deployment has an agreed scope, synchronisation approach and tested local workflow.
Coverage is agreed service by service.
Cloud email.
A local mailbox.
OPEN-SOURCE FOUNDATION mailcow
Keep agreed Gmail and Exchange Online mailboxes available through a local mail environment.
mailcow provides the independent mail services on your appliance. Authenticated synchronisation brings agreed mailbox content into that environment, so users can read and search previously synced messages when the primary cloud service is unavailable.
Designed into your plan
- Mailbox selection and provider permissions
- Local accounts, access and authentication
- A measured synchronisation interval
- Mail routing and reconnection procedures
Sending and receiving new internet email depends on connectivity, DNS and the mail-routing design. Calendars, contacts, shared mailboxes and other provider features are scoped separately; mailcow is not a feature-for-feature Exchange or Gmail replica.
Discuss email continuityCloud files.
Local access.
OPEN-SOURCE FOUNDATIONS rclone · Nextcloud
Make the files your business needs available on your own network.
Open-source synchronisation tools such as rclone connect to agreed Google Drive, OneDrive and SharePoint file libraries. A local file platform such as Nextcloud provides a workspace for the content held on the appliance.
Google Drive
Selected files and shared-drive content, with an agreed export approach for Google-native documents.
OneDrive & SharePoint
Selected user files and document libraries, with access rules and local working procedures defined in advance.
Cloud permissions, sharing links, version history and document collaboration do not automatically transfer into an equivalent local service. File formats, local editing and the handling of offline changes are agreed and tested as part of the deployment.
Discuss file continuityFreedom in the foundations
Open software.
Portable data.
A choice of what comes next.
We build the local service layer using established free and open-source projects. That keeps the architecture inspectable and helps you avoid a closed appliance ecosystem.
Standard interfaces, exportable data and documented configuration support a practical handover. Your local copy remains useful beyond a single supplier relationship.
A defined scope, not an assumption
Agree the capability.
Test the working day.
| Area | What we establish |
|---|---|
| Data | The mailboxes, folders and libraries included, and how recently they must be synchronised. |
| Access | The local applications, permissions and independent sign-in route your team will use. |
| Working | The local tasks that can continue, including any agreed document-editing or email-routing arrangements. |
| Return to cloud | How offline changes are reviewed, reconciled and returned to normal operation. |
| Cloud-only features | Any applications or features outside the local scope, including Teams or other SaaS services that need a separate plan. |
Planning after a disruption?
Start with the service that stopped.
Plan for the moment you need it
When the cloud stops,
your business shouldn’t.
Let’s define what your team needs to keep doing — and put a practical continuation plan in place.
Discuss your requirements