Connect your application and development environment.

Framework applications use supported database, identity, storage, and messaging integrations. Development tools on your instance can also coordinate projects in another stack; those projects retain their own integration and deployment requirements. Status labels below describe the listed platform integrations.

Separate your AI connection from application integrations

An external MCP client calls supported platform tools. The Createrun Agent in the Editor is a different connection path, with its own supported provider configuration. Choosing a client, choosing a model provider, and hosting the model are separate decisions.

Project knowledge can live on your instance while selected context is sent to an external model. Review that data flow and provider terms for the connection you plan to use.

Explore AI connection choices

IDENTITY

OpenID Connect single sign-on through the built-in identity provider.

ProviderProtocolStatusNotes
Built-in identity providerOAuth2 / OIDCLiveStandards-based; ships with every install
Active DirectoryDirect sign-in (Windows)BuiltMore than one AD domain can be configured
LDAPDirectory queriesLiveAvailable as a workflow task; sign-in uses the rows above
Local accountsUsername/passwordLiveAccounts kept on the instance itself
STORAGE
BackendUse caseStatus
Local diskSingle-instance, devLive
Network share (SMB/UNC), including NAS appliancesMulti-instance, on-premLive
Database blobAudit trails, small filesLive
AWS S3Cloud-native, large filesLive
Azure Blob StorageAzure-hostedLive
Google DriveWorkspace integrationLive
FTP / SFTPLegacy interchangeLive
DATABASE
ProviderStatusNotes
PostgreSQLLive · DefaultReference deployment, all internal services
Microsoft SQL ServerLiveEnterprise on-prem
MySQL / MariaDBLiveCommunity-standard databases
OracleLiveExisting Oracle estates
SQLiteLiveDev / embedded
IBM DB2Live
Microsoft Access (.mdb)LiveLegacy migrations
In-memory (testing)LiveTest fixtures, test environments
CACHE / MESSAGING / PAYMENT / OBSERVABILITY

Each item carries its status: Live ships today; Built means the code exists but waits on another feature; Planned means it is on the public roadmap. Where we have not confirmed a status for this page, the changelog is the reference.

Cache

  • In-memory cache Live
  • Database-backed cache Live
  • Redis Built supported release Planned

Messaging

  • SMTP transactional email Live
  • Outbound webhooks (HTTP) Live
  • Built-in background jobs · Status: see changelog

Payment

  • Stripe checkout for the Createrun Store Built
  • Custom payment gateway · Partner-built connector, on request

Observability

  • OpenTelemetry export (traces / metrics / logs) Live
  • Tempo / Prometheus / Loki / Grafana stack, self-hosted · Status: see changelog
  • Preconfigured alerting rules · Status: see changelog
CUSTOM INTEGRATION

If your system is not listed, every category above is built on a provider model: a connector is written once against your target system and plugged in without changes to the platform itself. Your own team can build it, or a Solution Partner can build it with you.

For engineering teams: each category exposes a single provider interface, and a connector is a standard .NET assembly the runtime discovers at startup. Provider interfaces are described on the Developers page and in the product documentation.

Developers page

Book a demo