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.Documentation Index
Fetch the complete documentation index at: https://docs.superblocks.com/llms.txt
Use this file to discover all available pages before exploring further.
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
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
- 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
- Customer-facing tools
- Self-service workflows
- Extending SaaS products with custom functionality
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
- Data applications
- Analytics and operational tooling
- Teams building directly on Databricks
Choosing a hosting option
| Hosting option | Primary advantage | Authentication | Integration effort | Best use case |
|---|---|---|---|---|
| Superblocks-managed | Fastest deployment with no infrastructure | Superblocks SSO (Okta, Entra, Google, etc.) | None | Internal tools and dashboards |
| Embedded apps | Runs inside existing applications | Custom (provided by parent app) | Medium | SaaS products and customer portals |
| Databricks apps | Native Databricks workspace experience | Databricks authentication | Low | Databricks-centric data applications |
- 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