Lagoria documentation
Run Lagoria in your own AWS account
Lagoria runs entirely inside your AWS account. You install it, keep it up to date and check its health with Lagoria Control, a small tool you start on your own machine when you need it.
Install LagoriaFrom an empty AWS account to a working Lagoria, step by step.
Health and diagnosticsSee what is running, what needs attention, and build a support bundle.
Upgrade and roll backMove to a new version, or back to the previous one.
TroubleshootingMessages you may see, and what to do about them.
How it fits together#
Each Lagoria release is one versioned container image, lagoria-control:<version>.
It contains everything that version needs. Your operator runs it on their own machine, with their
own AWS credentials, and opens it in a browser.
- Nothing of ours runs in your account. Lagoria Control stops when you close it. Lagoria itself (web app, API, data, search and AI) runs on AWS services in your account.
- Nothing is sent to us. When you need support, you build a support bundle, review it, and send it yourself.
- One version at a time. An image installs exactly its own version. To upgrade, you run the newer image; to roll back, you run the older one.
What gets deployed#
| Part | AWS service |
|---|---|
| Web app | AWS Amplify Hosting |
| Sign-in | Amazon Cognito, optionally connected to Microsoft Entra ID or Keycloak |
| API and business logic | Amazon API Gateway and AWS Lambda |
| Data and files | Amazon DynamoDB and Amazon S3 |
| Search | Amazon OpenSearch Serverless |
| AI | Amazon Bedrock (Claude Sonnet 4.6, Cohere Embed and Rerank) |
| Knowledge graph (optional) | Amazon Neptune Serverless |
Everything is deployed to eu-central-1 (Frankfurt).