Replies: 1 comment
|
Thanks for the detailed feedback! We understand the importance of having clearer boundaries between the Community Edition and Enterprise Edition, especially for community contributors. To provide some clarity, here is a general overview of the main areas covered by RAGFlow Enterprise Edition:
Please note that this is a high-level overview rather than an exhaustive or definitive feature list. Specific capabilities and their availability may evolve over time. Regarding community contributions: We welcome feature requests and contributions from the community. If you're unsure whether a proposed feature falls within the scope of the Community Edition or Enterprise Edition, we encourage you to open a Feature Request in GitHub Issues or Discussions before starting implementation. Our team can review the proposal and provide feedback on whether it aligns with the scope of the Community Edition. This should help contributors avoid spending time on implementations that may not be suitable for the open-source edition. We also appreciate your suggestions regarding edition comparison and migration documentation, and we'll take them into consideration as we continue improving our docs. Thanks again for your thoughtful feedback and support of RAGFlow! |
Uh oh!
There was an error while loading. Please reload this page.
Hi RAGFlow team,
Thanks for RAGFlow and concratulations on v1! Open core is a fair business model, and this isn't a request to move anything out of the Enterprise Edition (EE).
The question "what's the difference between the open-source and Enterprise editions?" has come up many times. The answer has always been to contact sales, and nothing has been written down publicly. With v1.0 the boundary is now enforced at build time (
//go:build !ee), and some features have moved from the Community Edition (CE) to EE. That makes three things worth writing down: where the boundary is, what moved across it, and whether community PRs on the EE side of it are welcome.Prior threads
Audit()as an EE-only no-op.The pattern is that the edition question gets a private answer, and PRs that touch the boundary stall without one.
What changed in v1.0
These things worked or existed in the CE before v1.0, and are now EE-only or no-ops in the CE build:
service_conf.yaml.template#L206-L228. The v1.0 CE is password-only (internal/handler/stub.go#L50,#L84). OAuth stubs were removed in #21614. SSO code was removed in #21584 and reverted in #21657, so its current status is unclear.These are EE-only in v1.0 according to the CE stubs, and as far as I can tell they aren't documented as such anywhere:
cmd/stub.go#L31table_construct_vh_stub.gointernal/entity/stub.go,internal/permission/stub.gointernal/common/stub.go#L54internal/engine/clickhouse/stub.gointernal/cli/stub.go,internal/admin/stub.go,internal/handler/stub.go#L67Neither the v0 → v1 upgrade guide nor the release notes mention any of this. Please correct me where I've misread the code.
Asks
CodeNotImplementedreads as a documented limit and not as a bug./pricing/detailsdisagree on tier names, prices ($29/$129 vs $59/$259), units (credits vs pages) and whether the Free tier gets API access. The only docs page labeled Enterprise Edition (registration whitelist) now returns 404.I'm happy to open a docs PR for (2) and (3) once the boundary is confirmed.
Thanks!
All reactions