Storage Provider Routing

Encore provisions PostgreSQL automatically as the primary store. Optionally bind your own PostgreSQL per tenant — writes are mirrored to both, reads always come from the Encore-managed DB.

Keep the permanent layer on Arweave while fitting the operational layer to each tenant.

Storage Providers are not about replacing Arweave. They let teams choose how operational metadata, indexes, and support systems are handled per tenant while keeping the core permanence model intact.

Value

Adapt to enterprise infrastructure reality

Some customers run the Encore-managed shared plane, while others require tenant-dedicated PostgreSQL for compliance boundaries.

Preserve one public contract

Clients keep the same API while the platform team chooses the operational backing store that fits each tenant best.

Create a stronger BYO-infrastructure story

This is useful when enterprise buyers need platform flexibility without compromising the permanent storage architecture.

For operators

• Register providers centrally and bind tenants deliberately instead of letting storage decisions drift ad hoc.
• Use capability flags to understand where behavior differs between shared and tenant-dedicated PostgreSQL providers.
• Pair with Connectors and SDK tooling when tenant-specific integrations also depend on tenant-specific operational state.

For buyers

• Useful for enterprises with strong opinions about operational databases and data-plane adjacency.
• Helps remove the objection that adopting Evercore means surrendering all infrastructure choices.
• Supports a cleaner multi-tenant story for managed deployments and higher-touch accounts.