ArboApp, powered by ArboID CloudSign in

ArboID identity platform + ArboApp integration console

One record for every person. Every app kept in step.

ArboID is where identity lives: users, groups, sign-in and application access. ArboApp connects ArboID to 97 business apps, so people are created, updated and removed everywhere from one source, with a full audit trail.

Integrations

97 apps ready to connect. Pick any two and build a flow.

Identity, HR, CRM, collaboration, developer, security, AI, cloud and finance systems. Each one lists exactly what it supports, so you know what ArboApp can create, update or deactivate before you connect it.

  • 1Password
  • Anthropic (Claude)
  • Asana
  • Auth0
  • Azure DevOps
  • BambooHR
  • Canva
  • ClickUp
  • Confluent Cloud
  • CrowdStrike Falcon
  • CyberArk Privilege Cloud / PAM
  • Datadog
  • dbt Cloud
  • Docker Hub
  • Dropbox Business
  • Dynamics 365
  • Figma
  • Freshdesk
  • GitHub
  • GitLab
  • Google Cloud IAM
  • Google Workspace
  • Gusto
  • HCP Terraform
  • HubSpot
  • Intercom
  • JFrog Artifactory
  • Kandji
  • LaunchDarkly
  • Microsoft 365 Copilot
  • Monday.com
  • Netlify
  • New Relic
  • Okta
  • OneLogin
  • Oracle Fusion Cloud
  • Palo Alto Prisma Cloud
  • PingOne
  • Rippling
  • Salesforce
  • SAP S/4HANA Cloud
  • Sentry
  • Slack
  • Snowflake
  • SonarQube
  • UKG Ready
  • Workday HCM
  • Zendesk
  • Zoom

All product names, logos and brands are property of their respective owners.

Two products, one system

ArboID knows who your people are. ArboApp makes every app agree.

The identity platform

ArboID

The system of record for identity. It decides who can sign in and what each person can reach.

  • Single sign-on with OpenID Connect for every application you assign
  • One user directory with groups, roles and application assignments
  • License tracking and orphaned-account detection
  • Managed tenants, so each organization signs in through its own identity provider
Explore ArboID →

The integration console

ArboApp

The bridge between ArboID and the 97 apps your teams use every day, built to keep accounts current without spreadsheets.

  • Connects ArboID to your business apps with stored, encrypted credentials
  • Creates, updates and deactivates users in each app, where the app allows it
  • Maps fields, runs on a schedule or webhook, and recovers failures from a dead-letter queue
  • Logs every change and every run with who, what and when
See all 97 integrations →
  1. Step 1

    Discover

    Import users, groups and app assignments from your identity provider and connected apps. Each person keeps the ID they have in every system.

  2. Step 2

    Reconcile

    Pick a primary profile source. ArboID holds one record per person and shows which apps they belong to, plus accounts nobody owns.

  3. Step 3

    Govern

    Changes flow out through ArboApp. Joiners are provisioned, leavers are deactivated, and the audit trail proves it.

Importing from identity providers works across supported providers. Writing changes back to the provider is available for Okta today; other providers are import-only.

Why ArboApp

Integrations are a business risk before they are a technical one.

Spreadsheets and one-off scripts

Data moves between systems through exports nobody owns. When a script breaks, nobody notices until a customer does.

No record of what ran

Finance asks which records changed last Tuesday. Without a trail, the answer takes a week and still is not certain.

Access that spreads

Credentials get shared in chat. Everyone can change everything. Leavers keep access longer than anyone admits.

What changes when integrations have a home.

One place to run integrations
Connect each system once, then build flows that move data between them.
Failures you can act on
Failed records land in a dead-letter queue. Fix the cause, then replay them.
Audit-ready by default
Every change and every run is logged with who, what and when.
Control for the right people
Roles, enforced two-factor sign-in and lockout protect production data.

The product

Four steps from disconnected systems to a running integration.

  1. 1

    Connect

    Add a system with its credentials. Secrets are stored encrypted and never shown again.

  2. 2

    Map

    Match source fields to destination fields and set transforms, so each system receives data in its own shape.

  3. 3

    Run

    Trigger a flow by hand, on a schedule, or from an incoming webhook. Each run is tracked as a job.

  4. 4

    Recover

    Records that fail go to the dead-letter queue with the reason. Replay them once fixed.

Inside the console

Connections

A registry of every system you integrate, with health and credentials in one place.

Field mapping

Visual source-to-destination mapping per flow, versioned with the flow.

Flows and jobs

Run history with row counts, durations and the exact error for each failure.

Schedules and webhooks

Cron-based runs, plus a signed webhook endpoint per connection.

Dead-letter queue

Nothing is silently dropped. Review, retry or discard failed records.

Audit log

A tamper-evident record of sign-ins, configuration changes and runs.

Security

Built for the people who answer for the data.

Role-based access

Platform admin, organization admin and member roles, each with scoped permissions.

Two-factor sign-in

Authenticator-app verification, with password change and MFA setup built in.

Account lockout

Repeated failed sign-ins lock the account until an administrator clears it.

Tenant isolation

Every query is scoped to your organization. Data never crosses tenants.

Access is by invitation.

Organizations are created and managed by the ArboApp platform administrator. Ask for your organization to be set up, or sign in if you already have an account.