Plug into the systems you already run.

Createrun connects to the databases, identity providers, storage, and messaging systems you already run — no rip-and-replace. Integrations are first-class citizens of the platform: configured centrally, versioned, and upgraded through the same controlled pipeline as everything you build. Current coverage and roadmap, honestly labelled, below.

IDENTITY

OIDC federation with Active Directory and Microsoft Entra ID.

ProviderProtocolStatusNotes
Createrun identity (built-in)OAuth2 / OIDCLiveStandards-based; ships with every install
Active DirectoryOIDC federationLiveMulti-AD coexistence supported
Microsoft Entra ID (formerly Azure AD)OIDCLiveConfigure as an external identity provider
Local Standard ProviderUsername/passwordLiveFor air-gapped instances
STORAGE
BackendUse caseStatus
Local diskSingle-instance, devLive
Network share (SMB/UNC)Multi-instance, on-premLive
Database blobAudit trails, small filesLive
AWS S3Cloud-native, large filesLive
Azure Blob StorageAzure-hostedLive
Google DriveWorkspace integrationLive
FTP / SFTPLegacy interchangeLive
QNAP NASSMB on-prem appliancesLive
DATABASE
ProviderStatusNotes
PostgreSQLLive · DefaultReference deployment, all internal services
Microsoft SQL ServerLiveEnterprise on-prem
MySQL / MariaDBLiveCommunity-standard databases
OracleLiveLegacy enterprise
SQLiteLiveDev / embedded
IBM DB2LiveMainframe interop
AccessMDBLiveLegacy migrations
InMemory / EmbeddedInMemoryLiveTest fixtures, sandbox
CACHE / MESSAGING / PAYMENT / OBSERVABILITY

Cache

  • In-memory
  • Database
  • Redis — Roadmap

Messaging

  • SMTP (transactional email)
  • Webhooks (outbound HTTP)
  • Built-in background jobs

Payment

  • Stripe (Marketplace checkout) — Roadmap
  • Stripe webhook handler — Roadmap
  • Custom gateway (partner-built connector)

Observability

  • OpenTelemetry (traces / metrics / logs)
  • Tempo / Prometheus / Loki / Grafana
  • Alerting pre-configured out of the box
  • Built-in observability stack (self-hosted)
CUSTOM INTEGRATION

Don't see your system? Every category above is built on an open provider model: a custom connector is written once against your target system and plugged in — no changes to the platform itself. Your team can build it, a Solution Partner can build it for you, or we can scope it together.

For engineering teams: each category exposes a single provider interface; a connector is a standard .NET assembly the runtime discovers at startup. Full interface documentation lives in the Developer Hub.

Developer Hub

Talk to us about a custom integration