Own database
Keep portfolio data in a PostgreSQL database you operate.
By arrangement only
Own hosting is agreed individually and enabled for your team by Zahlenwerk. After that, the Owner sees the page SettingsOwn-database hosting.
What lives where
| At Zahlenwerk | In your database |
|---|---|
| Sign-in, teams, permissions, billing | Positions, reports and metrics, valuations, cashflows, vesting |
| Uploaded original files | Companies, funds and SPVs, exchange rates |
| Encrypted credentials for your database |
What you provide
- A PostgreSQL database with SSL, reachable from Zahlenwerk's outgoing IP addresses (we'll tell you which).
- A role
zw_appwithSELECT,INSERT,UPDATE,DELETE. - A role
zw_migratewith schema privileges. You can revoke it after go-live, but it's needed again for later schema updates.
Example SQL is in the wizard under Before you start: what to provision.
The wizard
Connect your database
Host, port, database, role, SSL mode (require, verify-full) and password. Passwords are encrypted as soon as you save them.
Add the migration role
Credentials for the zw_migrate role.
Check the connection
Run probe checks reachability and privileges.
Create the schema
Zahlenwerk creates the tables.
Copy your data
Copies the existing portfolio data in one transaction. Safe to repeat.
Go live
From now on, Zahlenwerk reads and writes portfolio data in your database. The step is refused if the database is unreachable or the schema is out of date.
Every step is recorded in the audit log.
Back to the cloud
Switch back to cloud switches back to the Zahlenwerk database, but copies no data back. The confirmation points this out. Data created while running on your database stays there. Agree on a way back with us beforehand.
Your responsibility
- Availability, performance and backups of the database,
- SSL, network allowlisting and securing the roles,
- allowing schema updates promptly when Zahlenwerk announces them.
If your database is unreachable, portfolio features are unavailable for your team.