why there is no self hosted option

[saikethan27]

Summary

I'm raising this issue to request clarification about what parts of Supermemory are covered by the public MIT-licensed repositories and what is considered proprietary or part of an "Enterprise Deployment Package". I (and other community members) want to understand whether a complete self-hosted deployment is possible from the public codebase and what payment/host-ID requirements exist.

Observations (public facts)

• The main repository supermemory on GitHub is public and contains a LICENSE file showing MIT. (see repository). :contentReference[oaicite:4]{index=4}
• The supermemory-mcp repository is public and includes instructions for self-hosting. :contentReference[oaicite:5]{index=5}
• The documentation's Self-hosting page refers to an "Enterprise Deployment Package" which is "provided by the supermemory team" and states the deployment expects a unique NEXT_PUBLIC_HOST_ID supplied by the Supermemory team. This suggests some deployment artifacts (compiled bundle / Host ID / deployment script) are not published in the public repos. :contentReference[oaicite:6]{index=6}

Questions / clarification requested

1. Is the code in the public repositories intended to be a full, runnable self-hosted instance, or is the project intentionally open-core (open-source core + closed/proprietary enterprise artifacts)?
2. What exactly is included in the "Enterprise Deployment Package"? Please list which files/features are proprietary (e.g., compiled JS bundle, host-specific assets, auth code, analytics, etc.). :contentReference[oaicite:7]{index=7}
3. For developers who want to self-host for personal or non-commercial use: what is the supported path? Can they run a fully functioning instance using only the public repositories and configuration steps? If not, which components require an API key or Host ID from supermemory? :contentReference[oaicite:8]{index=8}
4. Is the MIT license intended to cover all code in the repo(s) except for the enterprise package? If so, could you please add a short "Open-core / Proprietary components" note to the README and the LICENSE or CONTRIBUTING docs clarifying this?
5. If there are security or compliance reasons for the closed components, would the maintainers consider publishing a clear list of differences between the community and enterprise editions?

Requested Actions

• Please update README / docs to plainly state whether this project is fully open-source or open-core and link to docs describing enterprise-only artifacts.
• If possible, add a public list of features that are enterprise-only (so users know what to expect).
• If the enterprise package is required for production self-hosting, please include an explanatory note and the contact path (sales/support) in the Self-hosting docs.

Links / evidence

• Main repo — supermemory: https://github.com/supermemoryai/supermemory. :contentReference[oaicite:9]{index=9}
• Supermemory MCP — supermemory-mcp repo. :contentReference[oaicite:10]{index=10}
• Docs: Self-hosting / Enterprise Deployment Package. :contentReference[oaicite:11]{index=11}

Why this matters

Community contributors want to know whether they can self-host and what the exact boundaries of the open-source code are. Clear documentation will prevent confusion and save maintainers time answering the same questions.

Thanks — looking forward to a clarification.

[capelo0]

It's critical to understand this. I also see Supermemory with lot of interest to have it self-hosted due to privacy reasons, but this OpenSource / paid obscure model doesn't seem to be the right approach. Please clarify this.

[MaheshtheDev]

Hey guys, we do have self hosting via enterprise as states in the docs .

However, will do update the README for more clarity

[SuperPauly]

It seems you still need to be an enterprise member to self host according to the docs.