Postver / Self-hosted deployment
Self-hosted deployment
Your servers.
Your procurement.
Your controls.
Run Postver in your own environment, next to the systems it serves. Keep invoices, supplier records, documents, backups and your AI route where you configure them.
Illustrative product view. Sample data.
A deployment your team can account for
Postver installs in your infrastructure. Data residency follows where you install it: your data center, your country or your cloud account. Your database and document storage remain part of your environment.
The “Where your data goes” view lists the destinations configured for the installation, including the database, documents, mailbox, identity provider, AI and backups. A new destination needs a second person’s approval before data flows to it.
Self-hosting gives your IT, security and finance teams a concrete deployment to review. They can inspect the systems and data destinations you choose rather than add another hosted repository for invoice and supplier data.
Identity and AI follow your configuration
Postver connects to your identity provider for SSO and SCIM, and to your own invoice mailbox. People work within the entities they are allowed to see.
The AI route is declared alongside the other data destinations. A suggestion identifies the model that answered and the destination of the data it used. A private model can run on your servers.
AI reads, drafts and suggests. A person decides, or a published, versioned rule makes the decision and appears on the record. Deployment control and decision evidence work together: knowing where a model runs does not replace knowing who approved an invoice.
Controls continue after installation
Approval rules move through draft, test, review and publish. Nobody approves their own change. Every action records who acted, on whose behalf and under which rule version.
The audit log is hash-chained so gaps can be checked. Backup visibility includes the age of the last recovery point, making recovery freshness part of the operating view rather than a hidden assumption.
Your infrastructure team should review database and object storage, mailbox access, identity, model routing, backups and ERP connectivity together. Those are the boundaries that determine where the installation runs and which systems it communicates with.
Start with your existing systems
Begin by installing Postver in your environment. Connect your ERP, starting with NetSuite, Coupa purchase orders where relevant, the invoice mailbox and your identity provider.
Bring in people, open invoices and contracts. An import dry run lists row-level problems before records are committed. The connection view shows what each connection can and cannot do.
In a deployment walkthrough, agree the entities and countries you need, the systems that own financial records, the model route and the people responsible for reviewing configuration changes.
Deployment questions
Is Postver a hosted SaaS service?
Postver is designed to run in your own environment, using the infrastructure and data destinations you configure.
Can we choose where our data lives?
Yes. Residency follows your installation and configured storage. The data-destination view lists where information goes, and new destinations require a second person’s approval.
Can AI run inside our environment?
Yes. The website’s model route includes a private model on your servers. Each suggestion identifies its model and data destination.
What should IT review before deployment?
Review database and document storage, identity, mailbox access, ERP connectivity, AI routing, backups and the approval process for changing those destinations.
Review the deployment with your team
Bring IT, security and finance into one walkthrough of the systems and controls.