Marmot Cloud

Marmot Cloud runs Marmot for you on a hostname of its own, with the database, backups and TLS managed. The catalog, the query language, the plugins and the MCP server work as they do everywhere else in these docs. Cloud adds access control per resource, secret stores that read from the vault you already run and pipelines that sign in to your cloud with no stored credential.

• Get startedLaunch an instance and catalog your first source
• InstancesThe console, compute units, plans and the lifecycle of an instance
• Invite your teamAdd people to your organisation and choose who runs billing
• Access controlGrant roles on the whole catalog or on one data product, asset or source
• Query accessChoose which sources answer queries and who can run them
• Single sign-onLet your team sign in through your identity provider
• PipelinesHow pipelines sign in to your cloud without a stored key
• Connect your cloudCatalog Google Cloud, AWS or Azure with no credential
• Secret storesRead passwords from your own secret manager at run time
• Private pluginsPublish your own plugins to your instance
• Security and isolationHow instances are kept apart and what Marmot stores