Your existing systems stay your existing systems.
Portenia pulls data live from your tools — through the connect agent inside your own network or through the public API. Your clients see everything in one place without you maintaining it twice.
The centrepiece: connect agent
Data from your own premises — without a VPN.
Behind most connections sits a lean container inside your network. It runs named queries and calls and returns results only — the cloud never sees SQL, credentials or internal addresses. Write-back actions travel the same path.
Public API
For everything coming in or going out.
A documented REST interface and outbound events — for any system that speaks HTTP.
REST interface with an OpenAPI description
Fully described; the machine-readable description lives at /api/docs/openapi.json and loads straight into tooling or a code generator.
Keys per tenant, with scopes
Every key belongs to one tenant and only to the scopes you grant it — read, write, administer. Plus a rate limit per key and cursor-based paging instead of page numbers.
Outbound events
Form submitted, record created or changed, message received, appointment created — as a call into your system, with an HMAC signature, retries and a delivery log. On request the call goes through your agent, keeping the destination inside your own network.
If none of that fits
Data sources directly in Portenia.
No core system? No problem. Maintain data here or let your clients deliver it through forms.
Enter it yourself or import a spreadsheet
Maintain data in the admin area or import a CSV — with column mapping and a preview before anything is written.
Forms write into the data source
A form in the portal files its answers as a new record. The client delivers, you have it structured — with a signature on the record if you want.
Fields by drag and drop
Assemble the structure visually — text, number, date, choice, references to other data sources. Validation and display rules included.
Two routes from practice
What connecting looks like day to day.
Example: insurance broker
The connect agent reads new policies from the broker management system through a named query and makes them available in the client’s portal — with a push notification if you want. Nobody resends policies; clients see the current state themselves.
Example: tax practice
The agent queries documents from the internal database on a schedule. Clients see the processing state in the portal and upload corrections directly. An outbound event carries them into the downstream system — no email ping-pong.
Sounds like your case?
Let us talk about your actual systems — which queries it takes and what should be written back.