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, wh

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 :)