> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ewake.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment options

> Where Ewake runs, who operates it, and who is responsible for what: an instance hosted by Ewake, or Ewake deployed in your own AWS account.

Ewake runs in one of two ways. Both run the same application, with the same agent, integrations and dashboard.

> [card] [Hosted by Ewake](https://docs.ewake.ai/architecture/hosted.md)
>
> A dedicated Ewake instance for your company, in Ewake's AWS account. Ewake runs and upgrades it. You sign in and connect your tools.

> [card] [Bring Your Own Cloud](https://docs.ewake.ai/architecture/byoc.md)
>
> Ewake deployed in an AWS account you own, from Ewake's open Terraform. Your data, your network and your Bedrock models stay in your account.

In both, Ewake reads your systems with the credentials you connect, and queries logs, metrics and traces live at the moment of an investigation. See [Permissions & Data Access](https://docs.ewake.ai/security/permissions.md) for what each integration can read.

***

## Compare the options

| | Hosted by Ewake | Bring Your Own Cloud |
| - | - | - |
| **AWS account** | Ewake's | Yours, dedicated to Ewake |
| **Region** | `eu-west-3` (Paris) | `eu-west-3` (Paris) |
| **Your instance** | Its own dashboard service, database, knowledge graph, workers, queue and secrets | The same, plus its own network, load balancer, database server and cluster |
| **Shared with other customers** | The AWS account, and the network, load balancer and database server your instance runs on | Nothing |
| **Language models** | Amazon Bedrock in Ewake's account | Amazon Bedrock in your account, with the models you choose |
| **Network exposure** | Public HTTPS at your instance's address | Public, or private behind your VPN or transit gateway |
| **Sign-in** | The providers Ewake configures for your instance | Your own OIDC identity provider |
| **Slack and GitHub** | Ewake's Slack app and GitHub App | A Slack app and a GitHub App that you own |
| **Upgrades** | Continuous, by Ewake | When you choose, by applying a new version |
| **Ewake's access to the infrastructure** | Full: Ewake operates it | None, unless you grant it |
| **Telemetry to Ewake** | Application logs, agent traces and sign-in events | None |

***

## Responsibility matrix

**Ewake** means Ewake does it. **You** means your team does it. **Shared** means both have a part, described in the row.

| Area | Responsibility | Hosted by Ewake | Bring Your Own Cloud |
| - | - | - | - |
| **Infrastructure** | Provide the AWS account | Ewake | You |
| | Create the network, compute and storage | Ewake | Shared: Ewake writes the Terraform, you apply it |
| | Raise AWS quotas (Lambda memory, Bedrock) | Ewake | You |
| | Decide who can reach the dashboard | Ewake | You |
| | Allow outbound traffic | Ewake | You |
| **Security** | Encrypt data at rest and in transit | Ewake | Shared: the Terraform enables it, in your account |
| | Hold application secrets and integration credentials | Ewake | You: they live in your Secrets Manager |
| | Run the identity provider used to sign in | Shared: your IdP, connected by Ewake | You |
| | Grant roles in the dashboard | Ewake, on your request | You |
| | Revoke a credential you gave an integration | You | You |
| | Revoke Ewake's access | Not applicable: Ewake operates the instance | You: Ewake has none unless you grant it |
| **Monitoring** | AWS audit logs and account security monitoring | Ewake | You |
| | Watch the instance's health and respond to failures | Ewake | You, with Ewake's support |
| **Data** | Govern the data in your source systems | You | You |
| | Back up the database and knowledge graph | Ewake | Shared: the Terraform schedules it, in your account |
| | Restore from a backup | Ewake | You, with Ewake's support |
| **AI models** | Enable models and accept their terms | Ewake | You |
| | Choose the model behind each tier | Ewake | You |
| **Software** | Release new versions | Ewake | Ewake |
| | Apply new versions | Ewake | You |
| | Connect integrations and configure the agent | You | You |
| **Costs** | AWS and Bedrock usage | Ewake | You |

> [!NOTE]
>
> Both options store integration credentials in AWS Secrets Manager, and every query to your systems runs with the credentials you connected. Read-only credentials keep Ewake from writing to those systems. Some writes remain, such as pull requests through the GitHub App and messages in Slack: see [How ewake takes action](https://docs.ewake.ai/security/permissions.md#how-ewake-takes-action).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.