Marketplace new app request

For teams working with professional video editors, it would be extremely valuable to integrate Frame.io directly into the HighLevel ecosystem. Frame.io is currently one of the most widely used tools by pro editors to: • share videos that are in progress, • collect precise feedback (timestamped comments and annotations), • manage smooth collaborative review cycles between clients and creators. 👉 Being able to connect Frame.io to a GHL account or sub-account, for example via the integrations panel or the media library, would: • centralize content production alongside GHL automations, • streamline collaboration between agencies, creators, and clients, • and bring a professional-grade video workflow into the HighLevel environment.

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.

To have the opportunity to modify the “story” of the agency's clients because I and my agency created sub-accounts manually in the past but they were never real customers of the account agency and therefore, today that I have actually started the resale of my customized software, the system shows me many more customers than I really are

Hi everyone, I’ve recently submitted an app to the Agent Review Marketplace and I’m currently waiting for approval. I want to make sure I’m following all the right steps to increase my chances of getting approved. Does anyone here have experience with this process? Specifically: What are the key requirements or common reasons apps get rejected? Any best practices or documentation I should double-check? How long does the review usually take? If my app gets rejected, can I appeal or resubmit? Any tips, insights, or examples from your own experience would be really helpful. Thanks in advance!

Wasn't sure where to put this request but I like to follow the updates and Changelog and think the experience could be made a lot better. https://ideas.gohighlevel.com/ Shorten the changelog updates on the main feed page. Currently, on the main Changelog page the entire update is posted to the feed. This is annoying as it makes it hard to scroll through the update history etc, especially when you release new templates and the thing scrolls forever. Instead, copy Clickup Canny setup and have your main feed be truncated posts that people can click through to read the full update: https://feedback.clickup.com/changelog More accurate Statuses for Planned etc. There are some changes that have been in planning for over two years. It would be nice if this was kept accurate and maybe things can only be marked as planned if they will be in pipeline in the next 6 months. That way people understand that it actually is underway. As it stands now, Planned status means nothing because it can still be years away.