Skip to content
SHAMPOO

Deployment

Software you install and operate.

SHAMPOO runs on infrastructure you control: one suitable server, an office server, a virtual machine, a private datacentre or customer-controlled hosted infrastructure.

SHAMPOO + MariaDB

Where it runs

Realistic deployment shapes.

Single host

The central service and MariaDB on one suitable machine. The simplest shape for evaluation, family use and small teams.

Office or site server

Run inside your own network position with your own backup regime. Workstations connect through their local adapters.

Private datacentre or customer-controlled cloud

Larger estates run the same binaries with their own topology, replication and recovery planning. Topology never changes what the software is.

Managed for you (DIFY)

AKADATA can provide a complete, professionally configured SHAMPOO server with the appropriate commercial rights: same software, operated for you.

What you provide

Requirements.

  • A host you control for the central service and MariaDB.
  • MariaDB reached only from the central host; no database credentials leave it.
  • TLS material for the service endpoint, provisioned by the operator.
  • Accurate clocks (UTC) and IPv6-capable networking where remote adapters connect.
  • One local adapter process per workstation and memory boundary.

Worth knowing

Notes for operators.

  • Internet access is not inherently required for SHAMPOO to remember, organise and serve your own information.
  • Already run MariaDB? Good. If you do not, installation and configuration are available as a service.
  • Backups, replication and recovery are the operator's regime to define; the platform keeps history that makes them meaningful.