Rovela 0.3.0: Billing, Team Permissions, and the Operator Console

What shipped in 0.3.0

Rovela 0.3.0 lays the foundation for running Rovela as a multi-tenant SaaS. It introduces subscription billing, a granular role and permission model, an operator console for the platform team, and bilingual documentation.

Subscription billing

Organizations can subscribe to the Pro plan directly from the dashboard. Billing is handled through a payment processor integration; invoices, receipts, and the billing portal are accessible under Settings. The free tier continues to exist with the same send limits; upgrading unlocks higher limits and access to advanced features.

Webhooks from the payment processor are processed in real time, so plan activations and cancellations take effect immediately without polling.

Eight member permissions

Every organization member is now assigned one of two roles — Admin or Member — and Admins can grant Members up to eight specific permissions: sending email, managing domains, managing mailboxes, reading logs, managing API keys, managing webhooks, managing templates, and managing suppressions.

This lets you give a support team member read access to logs without granting them the ability to change DNS records, or give a developer API key access without billing visibility.

Operator console

The operator console is a separate, TOTP-gated interface for the platform team. It shows organization health, plan status, usage metrics, and flagged accounts. Common support tasks — resetting a stuck send, re-running a DNS check — are available without touching the database directly.

Bilingual documentation

All product documentation is now available in English and Chinese. The language follows the locale already set in the dashboard, and each docs page is independently shareable with the locale baked into the URL.