eu-west-3 (Paris). Ewake provisions it, upgrades it and watches it. You sign in, connect your tools and work with the agent.
Each company gets its own instance. It is reached at its own address and keeps its data in its own database and knowledge graph.
Architecture
Dedicated to your company
- The application and the workers that run your investigations and scheduled agents, each with its own permissions.
- Your own database and your own knowledge graph, on encrypted storage.
- Your integration credentials, readable only by your instance.
- Your own address, a subdomain of
ewake.ai.
Shared with other customers
Hosted instances share Ewake’s AWS account and part of its infrastructure: the network, the load balancer, the database server, and the service that routes incoming Slack and GitHub events to the right instance. Each instance has its own credentials and permissions, and cannot reach another instance’s data.AI models
Ewake calls Amazon Bedrock in its own AWS account, through EU cross-region inference profiles. Bedrock does not use your prompts or outputs to train models. Ewake chooses the models and can change them with a release.Access control
- Users sign in through the providers configured for your instance: Google, Microsoft, GitHub or Slack. See Sign In.
- Ewake staff have administrative access to your instance, to operate and support it, and grant roles to your users.
- Ewake operators reach the infrastructure through Ewake’s AWS account. They do not need anything from you.
Telemetry
Ewake’s monitoring and agent-evaluation tools receive:- Application logs and traces, to watch the instance’s health.
- Agent traces, the prompts and tool results of a run, to debug and evaluate the agent.
- Sign-in events, to notice access problems.
Data security
- Your database and knowledge graph are encrypted at rest, and backed up daily.
- Logs, metrics and traces from your systems are queried live during an investigation, not copied into Ewake.
Network security
- Inbound: HTTPS only, at your instance’s address. Slack and GitHub events reach your instance through Ewake’s event routing.
- Outbound: to the systems you connect, to Amazon Bedrock, and to Ewake’s monitoring tools.