Use a representative example
Agree the work and required data. Begin with non-sensitive examples while checking the setup.
Self-hosting, security and data control
Cloud or self-hosted.
Your choice. Your control.
Choose cloud deployment or your own infrastructure. Define where data lives, who can access it and which connected services may receive it.
The deployment should fit your policies.
Cloud convenience. Self-hosted control.
Use the cloud or operate ActorLattice in your own environment. Confirm the supported setup, maintenance, updates and connected services before sensitive work begins.
- Choose and manage the hosting environment.
- Define who operates, updates and backs it up.
- Check any information sent to external AI or connected tools.
Choose how you run it.
Compare the responsibilities before you decide.
Use a cloud deployment.
Agree the hosting region and service terms without assuming every outside tool shares the same boundary.
- Application and records
- The agreed cloud environment
- Operations
- Ownership defined in your service terms
- Connected services
- Only approved accounts, actions and data
Deployment illustration. Confirm the supported release and operating responsibilities for your pilot.
Clear access.
Clear responsibility.
The first setup identifies who may read information, change records and approve an action.
The answers your firm needs.
Open evaluation questions. Confirm the answers in writing for the actual release and deployment before sensitive work. These are not published capabilities or certifications.
| Subject | What to confirm |
|---|---|
| Storage | Location, backups and access |
| AI services | Which providers receive which information |
| Permissions | Who may read, change and approve |
| History | Which decisions and actions are recorded |
| Retention | How long information is kept |
| Export and deletion | How the firm obtains or removes its information |
| Deployment | The hosting options actually supported |
| Support | Who helps when work is interrupted |
Set the limits before the pilot.
The checklist below is for evaluation. It is not a statement that every listed capability is available or certified.
Document the answers
Record the actual storage, model services, access rules and support arrangements for your deployment.
Approve the scope
Decide what information and actions may enter the pilot. Resolve open questions before sensitive work begins.
Support your GDPR responsibilities.
More control over the deployment. Not an automatic compliance certificate.
Self-hosting can support choices about data location and access. GDPR compliance still depends on the full processing operation: its lawful basis, contracts, security, retention, handling of rights requests and any international transfers. A hosting location alone does not answer those questions.
- Identify which personal data the process actually needs.
- Document access, retention and the providers involved.
- Assess external processing and transfers, even with self-hosting.
Bring the questions you must answer before a pilot.
We can establish which requirements fit the actual release and what remains to be resolved.
Discuss your requirements