Some things in Malveon are built and switched on. Some are built and switched off. Some are not built yet. Here is exactly which is which.
Kubernetes scale and restart
The backend exists: a real, RBAC-gated API that can scale or restart a Kubernetes deployment as part of incident remediation. It is not wired to any control in the product yet. Nothing to click today.
CI/CD automation actions
Cache purge, a feature-flag kill switch, one-click hotfix, and scale prediction all have a real backend: live, and every action is audit-logged. The UI surface for triggering them was pulled while the team designs a safer confirmation flow. Not reachable in the product today.
PagerDuty on-call push-sync
Building your own on-call rotation in Malveon and pushing it back to PagerDuty is fully built and tested. It is switched off for the initial launch. See the On-Call Scheduler and PagerDuty integration pages, they already cover the sync-from-PagerDuty direction that is live today.
AI-assisted decision writing (Malve)
Live today, on the Pro plan and above. Decisions are auto-detected from conversation for every plan, and on Pro and above a high-confidence detection now gets a real AI-generated title and summary, grounded in the source conversation, with prompt-injection guards and secret redaction in the pipeline. A lower-confidence detection, or any detection on the Free plan, still falls back to the honest templated title/summary instead of guessing.
Root-cause attribution
Live today, on every plan including Free. When an incident fires, Malviont resolves which deploy shipped, which commit it carried, which files that commit changed, and who owns them, across Vercel, Netlify, Render, Railway and GitHub Actions rather than one provider. It names an exact line when a Sentry stack trace or a failed build annotation points at one, and otherwise offers a separate "where to start looking" that is deliberately labelled as a starting point, never as a cause.
Project-level isolation and role customization (RBAC)
Planned for a future tier. Not yet built. To be precise about what this does and does not cover: the CEO Portfolio view is a real, live, shipped feature today, gated to leadership roles. What is not yet built is isolating data per project and customizing role permissions beyond the ten canonical roles.
Questions about a specific item
If a specific item here matters for your evaluation, email support@malveon.com and we will tell you exactly where it stands.