Separate the projects
Create a separate workspace and agent for each client. Agree on sources, fields, and who maintains the server.
For studios, agencies, and integrators
Manage the project. Keep the data with the client.
A studio prepares catalogs for several clients. Manage scenarios in Akmelo while collection and results stay on each client's server. This makes the location of exports and access rights clear from the start.
Every client has its own storage rules
One client uses a database in its data center; another uses S3 with a local provider. Moving every catalog into a shared studio repository is inconvenient. An agent runs near the intended recipient, with agreed access boundaries.
Client infrastructureSeparate storage
Project 1
Agent
Client database
Project 2
Agent
Client database
Project N
Agent
Client database
Turn a task into a process
Start with a small sample. Then control the rules, frequency, and result.
Connect the client's recipient
Add the database or storage connection in the agent's local interface. Grant access only to the required database, schema, or folder.
Hand over a working process
Check records, exports, and schedules. Leave the client instructions for backups, updates, and recovery.
What gets easier
Collection, storage, and delivery become one clear workflow.
Separate storage
One client's catalog does not enter another client's results database. Separate agents, permissions, and recipients support this boundary.
Clear handover
The client receives results on its side, while the studio can maintain scenarios within agreed limits.
Fewer manual file transfers
Exports are prepared on the client's schedule. The studio need not send a file from its own storage each time.
Results stay in your system.
Use your database through a suitable connector, local files, or a handler in your environment. For private recipients, an administrator configures approved network access or an SSH tunnel.
Agent
Client database
Client S3 storage
Local export files
Before starting
How should storage be arranged?
Separate servers should be paired with separate workspaces and permissions. Project settings and operational status remain on the platform. With mirroring disabled, records are not copied to Akmelo.
How data is separatedWhat should be agreed in advance?
- Who updates the agent and makes backups
- Which access the studio retains after handover
- What scenario logs may contain
Can one agent serve all clients?
The technical setup depends on project requirements. For independent clients, separate workspaces, agents, and recipients are easier to agree on. An agent alone does not replace access control.
Does the platform need SSH access?
Manual installation does not require it. The client's team can deploy the prepared stack. SSH installation is a separate option if the parties agree to it.
Test your workflow on one source.
First confirm that data reaches the intended recipient. Then add a schedule and more sources.