Athena is the fifth named version of Guara Cloud. If Persephone put more of the platform in your hands, Athena is about making those hands steadier: security that explains itself, storage that has a real operating surface, and deploys that fail with clearer next steps when production gets messy.
This release focuses on the parts of cloud work that usually become support tickets: knowing what is risky, understanding where data lives, changing services safely, and trusting the platform when something breaks. The result is a dashboard that gives you more control without asking you to learn more infrastructure.
Guara Shield
Findings, events, posture, scans, flow logs, and explanations in one security surface.
Guara Shield is now a full product area inside the dashboard. It brings together security findings, account and service events, posture reports, flow logs, service scans, secret exposure detection, runtime risk signals, and AI-generated explanations that translate evidence into action. Instead of a vulnerability list sitting off to the side, security now has a place to live: what happened, where it happened, how severe it is, and what you should do next.
Named Volumes
Create, attach, move, resize, and understand project storage from the dashboard.
Project storage is now a first-class resource. Named volumes let you create portable storage, attach and detach it from services, move it when supported, resize it within plan limits, and see volume state and health from the same workspace where you manage the rest of your project. Existing service storage is represented more consistently as volumes too, so persistent data no longer feels like a hidden implementation detail.
Security on your Home dashboard
Posture, findings, and recent events can stay in the first view you open.
Security signals can now sit directly on Home. Add widgets for posture, open findings, and recent security events, scope them to the account, project, or service you care about, and keep risk in view without turning every morning into a separate security review. For teams that live in the dashboard all day, Athena makes security feel like part of operations, not a different room.
Safer service changes
Ports, environment files, and runtime changes now have clearer guardrails.
Day-to-day service operations got less brittle. You can edit a service port from the UI, export
environment variables as a .env file, and use mixed-case variable names for frameworks that
expect them. The dashboard also got stricter about hiding internal platform details from users:
errors should tell you what to do, not leak the machinery that produced them.
Clearer failures, quieter operations
When deploys fail, the platform now works harder to explain the real reason.
Athena improves the way Guara Cloud classifies and reports the rough edges of production: terminal pod startup failures, storage quota boundaries, rollout drift, and background platform queues. More failures settle into specific, localised messages instead of vague pending states, and the internal health signals behind the product are quieter and easier for the Guara team to trust. The user-facing result is simple: fewer confusing failures, better next steps, and less time spent guessing.
And across the platform
-
Security events gained richer filters, grouped timelines, detail drawers, and auto-refresh.
-
Findings now have clearer state pills, safer evidence handling, and more direct links back to the affected project or service.
-
Catalog-backed snapshots now appear in the volume context where users already think about storage.
-
Project and service navigation is cleaner, especially around resource workspaces.
-
Service storage appears more consistently across service pages, project storage pages, and volume detail views.
-
Admin security triage got stronger, with account-level posture and per-user security context.
- Storage and observability limits are enforced more consistently by plan.
-
More screens show calm, generic user-facing errors instead of raw system details.
-
More background work is batched, deduplicated, or guarded, making busy accounts feel smoother.
And more, the kind of small platform polish that is easiest to notice when it is missing: sharper copy, stricter boundaries, quieter internals, and fewer places where users have to understand Kubernetes just to operate their own app.