Your organisation. Your instance. Your data.
For organisations that need it, we scope a private pilot with you: a dedicated Zaphiri with its own application, database, file storage and backups, managed by Zaphiri, with responsibilities written down and a cost you can read line by line before anything is agreed.
cedarline.zaphiri.com Your organisation's instance · example addressTwo ways to run Zaphiri. Same product.
It is the same Zaphiri either way: Best Hours, energy-aware planning, shared team projects and reports that show where the time really went, with plan features as on the pricing page. The only choice is whether we look after everything for you, or your organisation has an environment all of its own.
Zaphiri Cloud
Sign up today. We look after everything else.- Nothing to install, configure or maintain. Open it and start planning.
- New features arrive on their own, with no upgrade projects.
- Your plans stay yours; teammates see only the work you share.
- Start free and upgrade when it helps, at published prices.
A Zaphiri of your own
Your own environment. None of the work of running it.- Your organisation's own application, database and files, kept apart from every other customer.
- You set the rules: who joins, what administrators can see and when accounts close.
- Hosted where you need it, agreed with you up front.
- We would run it for you, with responsibilities agreed in writing first.
- Start with a short private pilot, and see it working before you commit.
A private environment you do not have to run.
An instance of your own
Application, database, files and transcription run separately for your organisation, not alongside other customers on Zaphiri Cloud.
Managed by Zaphiri
Monitoring, maintenance and security patches are part of the licence. Your IT team approves; it does not operate servers.
Staged updates
New releases reach the fleet in stages. A failed update stops the rollout before it reaches you.
Backups you have seen restored
Restores are rehearsed and recorded, and you can ask for the result.
A region you agree
Hosted on established cloud infrastructure, in a region set out in your proposal.
Implementation when you need it
We can connect the systems you rely on, scoped and quoted separately, with an owner for each connection.
Where everything goes, and who can see it.
Your proposal includes this map, filled in for your instance and the integrations you switch on.
| What | Where it lives | Who can reach it |
|---|---|---|
| Tasks, projects and docs | Your instance's database | Your members, by role; named Zaphiri operators for support |
| Files and recordings | Your instance's storage | Members with access to the task or doc |
| Transcription | A worker dedicated to your instance | No third party |
| AI features | The provider you choose, or switched off | Only what each feature sends; listed per feature |
| Backups | Separate storage, in the agreed region | Named Zaphiri operators, for restores |
| Integrations | Only those you switch on | Each one listed with what it reads and saves |
- Tasks, projects and docs Where it lives: Your instance's database Who can reach it: Your members, by role; named Zaphiri operators for support
- Files and recordings Where it lives: Your instance's storage Who can reach it: Members with access to the task or doc
- Transcription Where it lives: A worker dedicated to your instance Who can reach it: No third party
- AI features Where it lives: The provider you choose, or switched off Who can reach it: Only what each feature sends; listed per feature
- Backups Where it lives: Separate storage, in the agreed region Who can reach it: Named Zaphiri operators, for restores
- Integrations Where it lives: Only those you switch on Who can reach it: Each one listed with what it reads and saves
Four lines on one proposal. No surprises after.
Start with a short private pilot, then move to an annual licence for the scope you agree. Implementation and infrastructure are itemised alongside, so you see the full commitment before you proceed.
Private pilot
A few months in your own environment, for a monthly fee. Its setup payment counts towards implementation.
Implementation
Setup and adoption, scoped once. Bespoke integrations or major imports are quoted on their own.
Licence
One annual fee for the scope we agree: software, upgrades and standard maintenance. Not priced per seat.
Infrastructure
The hosting your environment runs on, billed by us as its own line at cost plus 30%.
Private hosting has no price list, because a ten-person team and a department need different resources. The licence covers the scope we agree with you, not a price per seat; if that scope changes materially, we requote. Tax is added where it applies. Zaphiri Cloud plans have published prices.
Clear rules for what an employer can see.
A Planning view inside an employer's instance is a work tool, not a private diary. Your agreement sets out what administrators can see, how people join and leave, and how long their records are kept. Everyone using it can read those rules.
Leaving is planned before you start.
Your proposal names what you can export, in which formats, who does the work and when the instance and its backups are deleted. You should never need to negotiate your way out.
Questions from IT and procurement.
Do we need private hosting?
Often not. Many teams are well served by Team or Team Pro on Zaphiri Cloud. Private hosting is for a specific requirement, such as where data must live, who can administer it, or how recovery is evidenced. We will tell you if we think a Zaphiri Cloud plan fits.
Can our existing Team workspace move into a private Zaphiri?
Not automatically. A private pilot starts in its own Zaphiri with a sample project. If you need existing work brought across, we assess and scope it with you before the pilot, and say plainly what it will and will not include.
Can we host it ourselves?
Not today. The starting offer is Zaphiri-managed, so patches, backups and restores stay with the people who build the software.
Is it dedicated hardware?
Your instance has its own application, database and storage on the cloud provider. Physical hardware is the provider's, as with any cloud service.
Who are the subprocessors?
The hosting provider for your region, the email provider for notifications, and any AI provider or integration you switch on. The full list comes with your proposal.
How large can a deployment be?
We size each instance for the team that uses it and agree the supported limits in writing.
Do you hold security certifications?
We answer security questionnaires directly and share the evidence behind each answer. We only name a certification once we hold it.
Start with one team.
Tell us about one workflow. We will show you Zaphiri with a sample project and recommend a Zaphiri Cloud plan or a private pilot, whichever fits.