# Self-Hosted Logs & Control-Plane Routing | Changelog

Source: https://wraps.dev/changelog/self-hosted-logs-and-control-plane-routing

![Wraps Logo](https://wraps.dev/wraps-light-logo.png)![Wraps Logo](https://wraps.dev/wraps-dark-logo.png)

](https://wraps.dev/)

[](https://github.com/wraps-team/wraps)[Log in](https://app.wraps.dev/auth?mode=signin)[Sign up](https://app.wraps.dev/auth?mode=signup)

Toggle menu

[← All changes](https://wraps.dev/changelog)

CLISelf-hostedJuly 2026

### Self-Hosted Logs & Control-Plane Routing

-   New `wraps selfhost logs` streams CloudWatch logs from a self-hosted install without opening the AWS console. Scope to a single source with `api`, `web`, or `workers`, tail with `--follow`, rewind with `--since`, and narrow with `--filter` or `--errors`
-   Fix: API commands now route to the control plane you signed in to. A self-hosted login no longer sends requests at the Wraps cloud API
-   Fix: `wraps status` prints your own dashboard URL on a self-hosted install instead of always printing the Wraps one
-   Fix: a self-hosted web domain can live outside Route 53, and adding a domain after the fact repoints the app URLs that unsubscribe, preference, and verification links are built from
-   Fix: the SST deployment variant normalizes its API URL, so the two deploy paths agree on what the API is called
-   Fix: the database connection pool is capped explicitly rather than inheriting node-postgres’ default of 10
-   Fix: SDK snippets printed by the CLI — deploy output, `sms init`, and the TUI deploy step — referenced a class and an `emails.send` method that never existed. They now show the real `email.send` API with an explicit region
-   Workers report failures to Sentry, and the self-hosted deploy workflow configures the Sentry DSN

CLI v2.30