Skip to main content
Choose where and how your Superblocks applications are made available to end users. Whether you’re building internal tools, embedding functionality into existing products, or deploying data applications to Databricks, Superblocks offers flexible hosting options that fit your organization’s needs.

What is hosting in Superblocks?

Hosting defines how users access a Superblocks app and how their identity is established when they do. It determines:
  • The URL or surface where users open the app
  • How users authenticate and are authorized
  • How the app fits into your existing product or platform experience
The hosting model you choose shapes the user entry point, authentication flow, and permission model, while allowing you to deliver the same app in different contexts.

Hosting options

Superblocks supports three hosting models.

Superblocks-hosted apps

Apps are accessed directly through Superblocks. Key characteristics:
  • Launched from the Superblocks UI or a direct app URL
  • Authentication and permissions managed by Superblocks
  • Minimal setup required to make apps available to users
Best for:
  • Internal tools
  • Administrative workflows
  • Operational dashboards

Embedded apps

Apps are accessed from within your product or website. Key characteristics:
  • Launched inside an iframe or embed component
  • User access integrated into an existing product experience
  • Authentication coordinated between your app and Superblocks
Best for:
  • Customer-facing tools
  • Self-service workflows
  • Extending SaaS products with custom functionality
Learn more about Embedded apps

Databricks apps

Apps are accessed from within a Databricks workspace. Key characteristics:
  • Launched as Databricks-native applications
  • User identity and permissions derived from Databricks
  • Access controlled by Databricks workspace settings
Best for:
  • Data applications
  • Analytics and operational tooling
  • Teams building directly on Databricks
Learn more about Superblocks Apps in Databricks

Choosing a hosting option

Hosting optionPrimary advantageAuthenticationIntegration effortBest use case
Superblocks-managedFastest deployment with no infrastructureSuperblocks SSO (Okta, Entra, Google, etc.)NoneInternal tools and dashboards
Embedded appsRuns inside existing applicationsCustom (provided by parent app)MediumSaaS products and customer portals
Databricks appsNative Databricks workspace experienceDatabricks authenticationLowDatabricks-centric data applications
As a general guideline:
  • Use Superblocks-managed hosting for most internal applications
  • Use Embedded apps when Superblocks must run inside an existing product or portal
  • Use Databricks apps when users primarily work in Databricks and expect applications to live there