Fits the stack you already run.
Identity, data and business systems connect through open standards, a REST API and connectors our engineers build in-house. Every entry below says whether it is available today or still in development.
- Available
- 9 integrations
- In development
- 8 integrations
- By arrangement
- 1 integration
Identity and access
Sign-in, provisioning and deprovisioning from your identity provider.
- SAML 2.0 single sign-onAvailable
- OpenID Connect single sign-onAvailable
- Microsoft Entra IDTested for single sign-onAvailable
- OktaTested for single sign-onAvailable
- Google WorkspaceTested for single sign-onAvailable
- SCIM provisioningWhere your identity provider supports itAvailable
- LDAP and Active Directory syncFor customer-hosted deploymentsIn development
Data in and out
Bring your history in, and keep other systems in step.
- REST APIAvailable
- CSV import with field mappingMapped with you during discoveryAvailable
- Signed outbound webhooksRetried for 24 hours, then held for replayIn development
- Developer portal and sandbox tenantIn development
Email and notifications
Where requests arrive, and where people hear about them.
- Email intake for MaeOne DeskAvailable
- Microsoft 365 and Google Workspace mailNotifications and ticket emailIn development
- Microsoft Teams and Slack notificationsIn development
Devices and IT operations
For MaeOne Endpoint and MaeOne Network.
- Microsoft IntuneRead-only device inventory and complianceIn development
- External monitoring toolsAlerts in through a signed webhookIn development
- Syslog forwarding to your SIEMIn development
Bespoke connectors
For the systems only your organisation runs.
- Connectors built by our engineersScoped and quoted with your projectBy arrangement
How every connector behaves.
The shared framework every connector will run on is being built as part of the platform. These are the rules it enforces, whoever writes the connector.
Credentials live in the vault
Entered once and stored as a reference — never in a connection’s settings, a log or an environment variable.
Only declared destinations
A connector can reach only the hosts it declares, so it cannot become a path for data to leave.
Same rules as the screen
Inbound data goes through the owning product’s validation, workflow and audit. A connector never writes tables directly.
Safe to re-run
Syncs are incremental and idempotent, so a failed window can be replayed without creating duplicates.
Failures are visible
A failing connection is marked degraded and its owner is told, with rejected items listed by reason.
Every key expires
API keys are shown once, stored as a hash, limited to explicit permissions and rotated with an overlap.