Integrations
Every system Cremit Platform touches
Explore scan sources, permission analysis, alert channels, SSO and directory connections. Check each integration’s setup and coverage before relying on it.
Scan Sources
Sources Cremit Platform scans for exposed secrets
Connect code repositories, document stores, and communication platforms. Cremit Platform scans content across them for credentials, API keys, and tokens.
GitHub
FeaturedScan enabled repositories available to the GitHub connection; review separate PR, conversation and GHCR coverage.
View Integration
GitLab
FeaturedScan enabled GitLab repository targets for credentials in reachable branch history, subject to job and access limits.
View IntegrationAWS S3
FeaturedFind credential patterns in supported, readable objects from connected S3 buckets.
View Integration
Bitbucket
Scan enabled Bitbucket Cloud repositories across reachable branch changes, with progress and skip checks.
View Integration
Google Drive
Scan enabled My Drive or shared-drive targets for credential patterns in supported, readable files.
View Integration
Jira
Scan enabled Jira Cloud projects for credentials in accessible issue text and supported attachments.
View Integration
Confluence
Scan enabled Confluence Cloud spaces for credential patterns in accessible page text, comments and supported attachments.
View Integration
Notion
Scan pages shared through the Notion OAuth connection, with target and scan-result checks for coverage.
View Integration
Slack (Messages)
Scan selected, accessible Slack channels and thread replies for credential patterns on a schedule.
View Integration
Permission Analysis
Analyzers for cloud permissions on discovered credentials
When Cremit Platform finds an AWS access key or a GCP API key, the analyzer maps what it can actually reach — IAM policies on AWS, API restrictions on GCP — so you can assess over-privilege and blast radius.
AWS (CloudFormation)
FeaturedPaidReview IAM user policy context for supported discovered AWS access keys through a connected account role.
View Integration
GCP API Key Restrictions
FeaturedPaidUse a connected service account to look up supported GCP API keys and inspect their API and caller restrictions.
View Integration
Alarm Channels
Where alerts land
Route detections and admin confirmation requests to the channel your team already watches. Slack, generic webhook, Telegram, or email.
Slack
FeaturedConnect a Slack channel through OAuth, then send alerts from selected Cremit alarm rules or workflows.
View IntegrationWebhook
FeaturedSend selected Cremit alarms to a public webhook endpoint with POST or GET and an optional receiver credential.
View Integration
Telegram
Route selected Cremit alarms to a Telegram chat ID through the bot configured by Cremit.
View Integration
Single Sign-On
SAML 2.0 and OIDC authentication for Cremit Platform
Authenticate Cremit Platform users through any SAML 2.0 or OIDC IdP, including Okta, Microsoft Entra ID, Google Workspace and Ping.
Directory Sync
Okta SCIM and Google Workspace directory data
Okta sends users and groups through SCIM. A user can pull Google Workspace directory data through its API. Check each provider’s last sync before using inactive-author context to investigate a credential; confirm its owner and rotate or revoke it at the issuer.
Okta SCIM
FeaturedEnterpriseReceive Okta SCIM 2.0 users and groups as directory records; review membership effects and sync status.
View Integration
Google Workspace Directory
FeaturedEnterpriseRead Google Workspace users, groups and active status into Cremit when an authorized user runs a directory sync.
View Integration
Need an integration we do not have?
Tell us about the source, channel, or identity provider you need. We prioritize roadmap items based on real requests.
Request an integrationReady to connect Cremit Platform?
Start on the free plan with your own scan sources, analyzers and alert channels. Contact sales if you need a custom integration.