MeldSignal
BUILT WITH TENANTSDB /
MeldSignal
MeldSignal
A signal intelligence product where structured inputs, account-specific workflows, and retained context need to stay distinct. Every customer runs in their own PostgreSQL database on TenantsDB.
Built with TenantsDB
THE PROBLEM
Signal workflows become risky when every account shares the same surface
Signal intelligence work is only as trustworthy as its boundaries. A platform like this ingests structured inputs, retains context over time, and runs account-specific workflows on top of both. In a shared-database design, all of that would live in the same tables, and every query would rely on application code to keep one account's intelligence from surfacing in another's results. The more workflows the product grows, the more code paths there are to get wrong.
MeldSignal sells to brands that ask hard questions about data separation. Answering "your data lives in its own database" and meaning it literally is worth a great deal, but running a physically separate database per customer normally demands dedicated platform engineering.
HOW IT USES TENANTSDB
Distinct customers, enforced at the database layer
Each MeldSignal customer gets their own PostgreSQL database, provisioned through TenantsDB automatically at signup. Signals, retained context, and workflow state stay inside the account that produced them, separated by physical database isolation rather than tenant_id filters. A query in one account cannot reach another account's data, because there is no shared surface to reach across.
Operationally, the fleet behaves like one database. When the schema changes, a single blueprint deployment rolls it across every customer database at once; a recent migration covered eleven customer databases and completed in seconds. Backups, GDPR deletion, and isolation controls come with the platform, so none of it had to be built or maintained in house. MeldSignal runs in production on this foundation today, with the entire database layer operated through one API instead of a platform team.