App Marketplace

Multiple Custom Menu Links for Marketplace Apps
Currently, Marketplace Apps are limited to a single Custom Menu object that lands in one of three places: Subaccount Only Agency Only Agency & Subaccount In our use cases, we would prefer to have separate custom menu objects. For example, our application has a client facing tool and an admin/agency tool. Our application already has the ability to distinguish which is being used - so we're taking advantage of showing each user (agency vs subaccount) the correct information, but we're limited in the naming convention of the Custom Menu object to be the same for both (even though they're doing drastically different things). Here's a simple use case: Marketplace App: SuperAgency Newsletter Magic Creation Extravaganza Purpose: Allows Agency to generate niche specific newsletters to their subaccounts Subaccount view: displays a dashboard showing the latest newsletters Agency view: displays the newsletter creation and selection tools as well as subaccount user/config menus Ideally, the subaccount should see "Newsletters" in their menu, while the agency should see the app name. This protects the Whitelabel through to the subaccount, while allowing the agency to easily identify the app/tool that they've installed. In this use case, our marketplace app would create two custom menu objects ("Newsletters" that displays only in the subaccount & "SuperAgency" that only displays in the agency account). This same functionality could be used to create multiple custom menu items per app (for those apps that handle many different functions) as well as gating each agency/subaccount entry point to a specific menu link (each custom menu object having their own url).
0
Allow Developers to Natively Host Apps and Backends Directly on GoHighLevel (No External Hosting Needed)
Currently, developers have to set up external hosting, servers, and databases (AWS, Firebase, Vercel, etc.) to power their custom GoHighLevel apps. This creates unnecessary friction, cost, and complexity—especially for small development teams and white-labeled SaaS owners who want to build native-style integrations directly within the GoHighLevel ecosystem. Feature Request: Enable developers to host both their frontend apps and backend services natively inside GoHighLevel’s infrastructure — just like how GHL currently handles snapshots, funnels, automations, etc. This could be done through: A native “App Hosting” environment in the Developer Portal. Built-in database and API hosting capabilities (e.g., access to a GHL-managed Firestore-like or Postgres-like database). Serverless function support for backend logic (similar to Firebase Functions or AWS Lambda). Secure GHL API integrations so hosted apps can directly interact with CRM data, contacts, workflows, and automations. Why This Matters: ⚡ Speed: No need to manage deployment pipelines or servers. 💰 Cost-Effective: Eliminates third-party hosting expenses for small developers. 🔒 Security & Compliance: All data stays within GoHighLevel’s infrastructure — simplifying compliance and user data handling. 🧱 Ecosystem Growth: Makes it easier for developers to innovate and release new apps faster, enriching the GHL marketplace. ♻️ True All-in-One Platform: Extends GHL beyond marketing automation into a full no-code/low-code app platform. Summary: Let’s empower developers to build, host, and scale apps 100% natively on GHL, removing the need for any external servers or databases. This would position GoHighLevel as not just a marketing platform — but a true all-in-one SaaS creation ecosystem.
0
Load More