​

Before You Begin

Confirm which plan you’re on before setting up Collate. Your setup path depends on it.

​

Account Types

Your plan determines how ingestion runs, what infrastructure you need, and which features are available.

​

Free Tier

For small data teams. Includes up to 5 users and 500 data assets on a multi-tenant SaaS deployment. The recommended ingestion path is Collate SaaS ingestion: connectors run inside Collate’s infrastructure and pull metadata from your sources over the public network. No infrastructure required on your end. Supports basic authentication only. If your data sources are not reachable from the public internet, you can optionally run a Local Ingestion Agent via Docker on your own laptop. This lets you push metadata from inside your network without any cloud infrastructure.

​

Premium

For teams and small businesses. Includes up to 25 users and 5,000 data assets on a single-tenant or Hybrid SaaS deployment with an 8-hour data refresh frequency. Ingestion can run fully within your own infrastructure using the Hybrid Ingestion Runner: a Kubernetes-based agent that never exposes your internal network to Collate. Includes SSO, Automated PII Classification, and APIs & SDK support. Your admin receives credentials from the Collate support team by email.

​

Enterprise

For complex use cases and enterprise-wide initiatives. Includes up to 50 users and 10,000 data assets (unlimited options available) with hourly data refresh frequency. Supports Single-tenant SaaS, Hybrid SaaS, or Private BYOC (bring your own cloud) deployment on AWS, GCP, or Azure. Includes all Premium features plus custom integrations, audit logs, AWS VPN add-on, and dedicated support. Contact the Collate team for credentials and deployment setup.

​

What to Prepare

• Your Collate workspace URL and login credentials
• Connection details for at least one data source (host, port, and credentials)
• Premium and Enterprise: Network access to deploy the Hybrid Runner on Kubernetes 1.28 or later
• Premium and Enterprise: Your identity provider details for SSO configuration
• Enterprise (BYOC): An AWS, GCP, or Azure environment for private cloud deployment
• Free Tier only: Docker installed on your laptop if you plan to use the Local Ingestion Agent

​

Browser Requirements

Collate works in any modern browser. The following browsers are recommended for the best experience:

• Google Chrome (latest)
• Microsoft Edge (latest)
• Mozilla Firefox (latest)
• Safari (latest)

​

Supported SSO Providers

Collate supports single sign-on (SSO) via the following identity providers:

• SAML 2.0: Okta, Azure AD, Google Workspace, and other SAML-compliant providers
• OIDC (OpenID Connect): Auth0, Keycloak, and other OIDC-compliant providers
• Google OAuth
• Azure AD
• Okta
• AWS Cognito
• Custom OIDC providers

SSO configuration is performed by an Admin in Settings > Authentication. Premium and Enterprise accounts may need to configure their SSO redirect URI to include the Collate callback URL provided by the Collate support team.

​

Required Roles and Permissions

Collate uses a hybrid Role-Based and Attribute-Based Access Control (RBAC + ABAC) model. Assign the base role that matches each user’s primary job, then layer on additional permissions as needed. An organization can have multiple Platform Administrators, each managing specific teams and departments independently. For more information about how to create custom roles, define fine-grained policies, and manage access control across your organization, see Advanced Guide for Roles and Policies

​

Connecting to Your Collate Instance

To access your Collate workspace:

1. Open your browser and navigate to your Collate workspace URL. This is typically in the format https://<your-org>.getcollate.io.
2. Sign in with your credentials. If SSO is configured, you will be redirected to your identity provider.
3. After signing in, you will land on the My Data home page (or the Collate AI Chat experience in Collate 2.0).

​

Select Your Setup Path

All plans end at the same place: a connected data source, ingested metadata, and an invited team. Select the column that matches your setup.

​

What Admins Can Do

Administrators can configure and manage every area of the platform:

• Users, Teams, and Roles — Invite users, create hierarchical teams, assign roles, and define fine-grained access policies.
• SSO & Authentication — Set up single sign-on via Okta, Azure AD, Google, Auth0, SAML, OIDC, or custom providers.
• Services and Ingestion — Connect data sources, configure ingestion pipelines, and manage service connections.
• Applications — Run platform-wide jobs — Autopilot, Reverse Metadata, Query Runner, and others.
• Search and Personas — Configure search indexing, tune relevance settings, and customize persona landing pages.
• Custom Properties and Data Insights — Extend data models with custom fields and monitor data health across sources.
• Notifications — Set up notification rules and alert channels for data events and pipeline activity.
• Audit Logs — Review a full audit trail of user actions and platform changes (Enterprise).
• Billing and AI Credits — Monitor AI credit consumption, track plan usage, and troubleshoot blocked agent runs.

​

What’s Next

1. Ingest Your Data: Connect your first data source using SaaS ingestion, the Hybrid Runner, or a Local Ingestion Agent.
2. Configure Metadata Ingestion: Set up ingestion workflows to pull schemas, lineage, and usage from your connected sources.
3. Invite Users: Add your team, assign roles, and configure access so everyone can start collaborating on data.
4. Explore Features: Discover data discovery, lineage, quality, governance, and AI features across the platform.