Business
storage.
Simplified.

Business cloud storage for everyday work

You open a document at the office, update the figures and save it. A colleague with access picks it up on their own computer. There is no new attachment to send and no need to explain which of five copies is current. DataServer is designed to move changes between devices while keeping file work in a familiar environment: File Explorer on Windows, Finder on a Mac, and the applications you already use to edit your documents.

During setup, we will agree on a clear structure such as Documents, Jobs, Shared and Accounting. Folder names should reflect your work so a new colleague can find their way around. Each company will have its own space, with shared folders assigned only to the people who need them. Working across several companies should not mean one confusing directory that everyone can open.

A visible sync status is part of that everyday experience. An online-only file needs a connection; a document selected for offline access remains on the device. If two people edit the same thing at once, the conflict needs to be shown and resolved. We do not promise conflict-free simultaneous editing or a replacement for every feature in an office suite.

Share invoices and receipts with your accountant

Imagine an accounting practice with several clients. Each has a separate folder and the same straightforward way to hand over documents. A client working at a computer saves a PDF invoice directly to their own space. A client with a paper receipt opens their personal link on a phone and sends a photo. The accountant should find both documents under the correct company, without searching email threads and messages spread across different apps.

We propose a simple folder workflow: Received, To process, Processed and From your accountant. These labels help people find their way; they do not replace the accountant's professional judgement. The submission date may differ from the document date and the relevant accounting period. A receipt found late should not automatically be assigned to the wrong month. Classification and processing remain the accountant's responsibility.

The return journey to the client matters just as much. Outputs, a list of required documents or agreed instructions can go into From your accountant, so the client knows where to look. Access for each member of the practice should follow their assigned companies: not every accountant needs to see every client. We plan to validate the precise workflow in an internal pilot before wider use.

A handoff you do not have to explain every month

Submitting documents often comes with a simple uncertainty: where do I send this, and did it arrive? That is why the personal link should be set up in advance. A business owner opens their shortcut, photographs the whole receipt, checks that it is readable and sends it. There is no company to select, accountant to search for or sharing setting to configure. The destination follows the assigned account or link rather than an address typed by hand.

The photo should show the entire document, including the important details. We recommend good light, a flat surface and a check of the preview before sending. An unreadable image may still need to be replaced or clarified by the accountant. Without a connection, or if a transfer fails, opening the page alone does not mean delivery. Confirmation should appear only after the document has been successfully stored on the server.

An upload link is for submitting documents, not browsing the company's files. An administrator should be able to revoke it when it is no longer needed. Treat it as permission to submit: do not publish it, and request a replacement if it is shared by mistake. The first version focuses on straightforward storage and clear confirmation, without promising automatic extraction, bookkeeping or a statutory archive.

Start with a small space that makes sense

A good start does not mean moving every file at once. First, we will look at the work people actually do: how many devices they use, which folders they share and how they communicate with their accountant. We will select a limited set of documents and agree where the current working version belongs. Original data should be kept until the new workflow has been tested in practice. That helps establish whether the service saves time even for people who are reluctant to learn new tools.

Management also needs to cover ordinary business changes. A colleague joins, an accountant changes or a computer is replaced. These situations should not be handled by giving everyone the same password. The design uses personal accounts, assigned folders and the ability to revoke future access. Copies that have already been downloaded remain on the device; disabling an account cannot remotely erase them.

Version history can help with an accidental edit, while an independent backup supports recovery from a larger problem. Retention periods and the recovery process must be agreed and tested. We also want a usable export when leaving the service. DataServer is being developed as a managed way to simplify everyday work. Public storage availability, pricing and binding terms will follow once the core scenarios have been validated. Everyone should be able to understand the workflow.

Is file sync the same as a backup?

A synchronised business drive is intended to make working files available across devices. Changes can also spread when someone accidentally overwrites or deletes a document. That is why our design separates the shared drive, version history and independent backups. Recovery procedures and retention periods will be agreed before the pilot; file sync alone does not replace a backup.