Hey, we shipped a few new things this week. Here's a quick look at what's new.

Docs Reorganization

We reorganized our documentation to make things easier to find. Docs are now grouped by category - Deploy, Build, Security, Observability, Networking, Billing, CLI, and Public API - each with a clear structure and consistent ordering.

If you haven't visited our docs in a while, take a look. Everything should be easier to navigate now. https://docs.quave.cloud

Terminal Access to Your Workloads - No SSH Required

We added secure terminal access directly to your running workloads inside Quave ONE.

You can now open a browser-based terminal session into any running container, just like you would SSH into a server - but fully Kubernetes-native. There is no SSH server, no exposed ports, and no extra configuration. Access is handled through Kubernetes itself, following your existing permissions and role policies.

How it works

Navigate to your app environment, go to the Containers view, and click the actions dropdown on any running container. Select Terminal, and you're in.

Sessions have a 15-minute idle timeout with a visible countdown timer that resets every time you interact. All terminal input and output is encrypted at rest. Each session is isolated - you can only see your own sessions.

What you can do with it

• Debug applications in real time
• Run one-off commands inside containers (migrations, cache clearing, maintenance scripts)
• Inspect files, logs, and runtime state
• Check memory usage, running processes, or network connections

No need to manage SSH keys or bastion hosts. Everything is secure, auditable, and aligned with Kubernetes best practices.

Terminal access requires the Pod Access role (more on roles below) and the feature must be enabled on your account. Contact us if you'd like to enable it.

Custom Webhook Notifications

You can now send notifications to a custom webhook URL whenever events happen in your environments.

Webhooks send HTTP POST requests with structured JSON payloads. You can use them to integrate Quave ONE with CI/CD pipelines, incident management tools like PagerDuty, custom dashboards, or anything that accepts HTTP requests.

Supported events

• Environment status changes - build started, deploy succeeded, deploy failed, and other status transitions
• Container restarts - when a container restarts unexpectedly (rate-limited to avoid noise: first restart immediately, then at most once every 3 hours)

Payload details

Every webhook payload includes account, app, and environment identifiers, a direct link to the environment in Quave ONE, and event-specific fields.

For status changes, you get the status, a human-readable label, the hostname, and the Docker image. For container restarts, you get the container name, restart count, exit code with a human-readable label (like "OOMKilled"), and an error message when available.

How to set it up

Go to your account Notifications settings (or environment-level Notifications for per-environment control), enable the Webhook toggle, enter your URL, and check which events should trigger webhook calls.

You can test it with a service like webhook.site before connecting to your production systems. Delivery is fire-and-forget with no retries, so keep that in mind when designing your integration.

Webhooks work alongside email and Slack notifications. You can mix and match channels per event type.

New User Roles

We expanded our role-based access control. Quave ONE now has five distinct roles you can assign to account members:

• Admin - full control over account settings and secrets
• Technical - for team members involved in technical operations
• Billing - receives billing-related email notifications (payment failures, invoice reminders, savings plan updates)
• Pod Access - allows opening terminal sessions inside running containers
• Manage Members - allows inviting new members, updating roles, and removing members from the account

Users can hold multiple roles, and roles are per-account - the same person can have different roles in different accounts. When you create an account, you get all roles by default. Role changes take effect immediately.

To manage roles, go to your account Members page and click the role badges next to a member's name.

This gives you more control over who can do what, without the all-or-nothing approach of just having admins and non-admins.

That is it for this week. See you soon.