Studio or Teams? Choose your Rowset
Two real workflows: a local workspace for one person and governed access for an organization.
Studio: you own the workspace
Studio runs on your computer with no Rowset cloud account. It combines a SQL editor, schema browser, row editing, notebooks, personal history, personal policies, managed transactions and optional row backups. Credentials and workspace data are encrypted locally.
SELECT id, total, status
FROM orders
WHERE customer_id = 1001
ORDER BY id DESC
LIMIT 100;SELECT id, total, status FROM orders WHERE customer_id = 1001 LIMIT 100;
Teams: access is shared and governed
Teams is a commercial, self-hosted access layer. It offers user roles, connection permissions, shared policies, approvals, masking, row filters, centralized audit and PostgreSQL, MySQL and SQL Server client gateways.
A common case is allowing analysts to query production data while masking sensitive columns and requiring approval for a risky write. This is a policy and access workflow, not merely a different SQL editor.
Which edition fits?
Choose Studio for a personal local-first IDE and optional post-commit row Restore. Choose Teams when several people need common rules and accountable access to production. Teams costs $10 per user per month for teams of up to five. Larger teams can discuss volume pricing with Rowset. Row backups and Restore are not available on its shared server yet.