Bring your own database
Run SetFlow against a PostgreSQL-compatible database your institution owns. Your data, your control plane.
What BYODB is
Most SetFlow customers are happy with our managed database — it's encrypted, backed up, and operated to a high standard. Some institutions have residency, compliance, or governance requirements that mean they'd rather operate the database themselves. Bring your own database (BYODB) is the answer.
Who it's for
- Universities with strict data-residency policies.
- Districts whose general counsel requires sole custody of student records.
- Government and defense-adjacent organizations under specific compliance frameworks.
- Enterprises that already operate a managed PostgreSQL fleet and want to add SetFlow to it.
How it works
You provision a PostgreSQL-compatible database in your environment of choice. We hand you the SetFlow schema and migrations. You point SetFlow at your database via a connection string — over a private network connection (peering, PrivateLink, or a customer VPN, your choice). All writes go to your database; all reads come from your database.
Privacy
Requirements
- A PostgreSQL-compatible database, version 14 or later.
- A private network path between SetFlow's service and the database.
- Encryption at rest (AES-256 or equivalent) and TLS in transit — most managed providers default to both.
- Adequate provisioned capacity. We'll size with you based on user counts.
What it doesn't change
BYODB changes where the database lives. It doesn't change SetFlow's product surface, the AI features, or the way users interact with the platform — those stay identical. AI inference still runs on our side; if you also need on-premise AI, that's a separate conversation.
Note
Tip