Private Apps
A private app is a custom Webflow app for a specific workspace or custom implementation. This guide explains how private apps work and how to manage them.
What are private apps?
A private app is a custom Webflow app built for a specific workspace or custom implementation. Private apps are fully functional Webflow apps, but they are not intended for broad distribution across multiple workspaces or as a substitute for public Marketplace distribution, unlisted public app distribution, or pre-launch testing.
Private apps are workspace-specific or custom apps, so they don’t use Marketplace listing visibility. Marketplace listing visibility applies to public Marketplace apps — a public app may be listed or unlisted where Webflow supports that distribution model.
When should you use a private app?
Private apps are a great option for:
- Internal apps used by a single organization
Apps built for use within a single company or organization. These apps can help streamline internal workflows, integrate with company systems, or provide specialized functionality for employees. - Custom apps developed for a specific client
Custom solutions developed for a specific client’s workspace or implementation. These apps are tailored to meet particular client needs and aren’t intended for broader distribution.
Testing your app before launch?
Testing before launch is separate from creating a private app. If you want to validate an app with external users before publication, use the user testing process instead of submitting a private app.
Key characteristics
- Not visible on the public Marketplace. Private apps do not have a Marketplace listing page.
- Intended for a specific workspace or custom implementation, not broad multi-workspace distribution
- Access controlled via direct install URL sharing
- Maintains full API capabilities and integrations
- Can be monetized (subject to standard Marketplace terms)
About direct install
Direct install is an installation access path. It is not an app type, not a Marketplace visibility setting, and not the same as a private app. Direct install may be used only when that install path is supported for the app’s approved distribution model.
Publishing a private app
Submission process
- Submit your app through the standard Marketplace submission form
- Select the “Private” option in the “Marketplace Visibility” section of the submission form
- Complete all required app information and documentation
- Submit for review
Private apps undergo the same rigorous review process as public apps to ensure quality and security standards are met.
Managing access
Once your private app is approved:
- You’ll receive a unique Install URL for your app
- Share this URL directly with intended users
- Only users with the Install URL can access and install your app
Best practices
- Maintain clear documentation for your private app users
- Keep track of who you’ve shared your Install URL with
- Regularly communicate updates and changes to your users