Enterprise
Same product. Your infrastructure, your rules.
Where the data lives, who sees it, and what if we are gone.
Deployment
Cloud or on-premises — the same build either way
There is no cut-down self-hosted edition. On-premises runs the identical image our cloud runs.
| PulseUp Cloud | On-premises | |
|---|---|---|
| Hosting | Managed by us | Your server, VM or private cloud |
| Data location | Our managed storage | A single directory you control |
| Upgrades | Applied by us | You choose when, from a tagged release |
| Model endpoint | Configured by us or you | Any endpoint — including one inside your network |
| Outbound traffic | HTTPS to the app | Model endpoint only, or none with a local model |
| Backups | Nightly with retention | Your existing tooling, one volume |
| Custom domain and subdomains | ||
| Access to the versioned API | ||
| Suits | Firms who want it live this week | Institutions with data-residency rules |
The enterprise surface
Four things procurement will ask about
On-premises
Four containers, one volume, one command. Runs on modest hardware and upgrades on your schedule.
On-premisesSecurity & governance
Tenancy as a data-model property, workspace roles, append-only audit, and an AI usage ledger.
Security & governanceAPI & integrations
A frozen, versioned REST contract with per-device bearer tokens and a published schema.
API & integrationsOnboarding & support
Migration, catalogue design, training, and a written response commitment.
Onboarding & support
Tenancy
One deployment can hold the whole group
A workspace is the tenancy boundary: every domain row belongs to exactly one, and a record from another workspace is simply not found — not forbidden, not hinted at.
That makes offices, subsidiaries and separate practices safe to host together, each with its own catalogue, seats, clients and documents, while platform staff retain a console for the operational tasks that must cross the line.
- Workspace roles — owner, admin, member — distinct from vendor staff
- Seat limits enforced at every door where a seat is taken
- Suspension and reactivation without touching a byte of data
- Subdomain per tenant on-premises, when you want one
- Sama AdvisoryBusiness24 / 30
- Kavir PartnersTeam7 / 10
- Group TreasuryEnterpriseunlimited
What we do not claim
Honest gaps, stated up front
You will find these in our documentation too. We would rather lose a deal than win one on an implied certification.
- We do not hold SOC 2 or ISO 27001 certification today; we will describe our controls in detail and let your team assess them
- There is no packaged SSO or SCIM integration yet — authentication is email and password
- In-product checkout is built but not yet transacting; Enterprise is invoiced directly either way
- Valuation models and generated client deliverables are roadmap surfaces, not shipped features
- Automated tenant data export is not built; export is an operator task we run on request
Enterprise questions
What happens to our data if we stop being a customer?
On-premises, nothing — it is already yours, in one directory. On cloud, we produce a full export of your workspace's database and files on request, and delete the deployment copy once you confirm receipt.Can we run it without any internet access at all?
Yes, provided the model endpoint is inside your network. Document reading, transcription and the assistant all point at a configurable endpoint; everything else is local to the deployment.How do upgrades work on-premises?
You pull a tagged release and rebuild. Database migrations run at startup and are tested on both supported database engines before release.Do you support single sign-on?
Not yet. Authentication is email and password, argon2-hashed, with revocable sessions. If SSO is a hard requirement, tell us during evaluation — it is a roadmap item and your requirement will shape it.
Talk to us about your deployment
Bring your security questionnaire, your network constraints and your timetable. We would rather answer the hard questions before a pilot than after one.