3 ms·

Hi there! ParadeDB author here. We don't believe AGPL should prevent you from self-hosting for your own internal usage. We see ourselves as becoming a Postgres

Hi there! ParadeDB author here. We don't believe AGPL should prevent you from self-hosting for your own internal usage. We see ourselves as becoming a Postgres-based Elasticsearch alternative, primarily used internally for observability, etc. If you are interested in using ParadeDB to power your own product, or would prefer a different license, we'd love to hear from you. You can reach me directly at phil@paradedb.com. We spent a lot of time evaluating which license to use, and decided to follow the footsteps of Citus Data and go with a standard OSS license while ensuring that we can't be hosted on public clouds without a partnership. Hope this helps!

Sytten 3y ago
I am not right now looking for this but say I want to add a search function to my program it would be nice to be able to add the extension to my existing DB for a fee (say 30-50USD/month) without having to spawn a whole instance. I hope cloud providers offer the service but what I have seen is they only support fully OSS which is annoying. I guess it is fine if you plan on being acquired like citus.
- philippemnoel 3y ago
  This is interesting. We've been seeing a pretty split desire where some companies would prefer ParadeDB installed as an extension in their existing database, while others would prefer ParadeDB as a separate search node (for independent scaling, recovery, performance, etc.) We expect production-scale ParadeDB to be used as a separate search node getting logical replication from your primary Postgres. This would give you easy-to-maintain and scale services while benefiting from isolation of services (so your search can't take down your primary database, etc.) We would be open to what you describe and happy to work it out. But we are currently thinking of prioritizing separate hosting of ParadeDB. It's early, though, and still unconfirmed what customers will prefer :)

Sytten 3y ago

I am not right now looking for this but say I want to add a search function to my program it would be nice to be able to add the extension to my existing DB for a fee (say 30-50USD/month) without having to spawn a whole instance. I hope cloud providers offer the service but what I have seen is they only support fully OSS which is annoying. I guess it is fine if you plan on being acquired like citus.

philippemnoel 3y ago
This is interesting. We've been seeing a pretty split desire where some companies would prefer ParadeDB installed as an extension in their existing database, while others would prefer ParadeDB as a separate search node (for independent scaling, recovery, performance, etc.) We expect production-scale ParadeDB to be used as a separate search node getting logical replication from your primary Postgres. This would give you easy-to-maintain and scale services while benefiting from isolation of services (so your search can't take down your primary database, etc.) We would be open to what you describe and happy to work it out. But we are currently thinking of prioritizing separate hosting of ParadeDB. It's early, though, and still unconfirmed what customers will prefer :)