ClientShare

Open source and self-hosted

Want more control? Self-host the same workflow.

Hosted ClientShare is the fastest path for most small firms. The open-source self-hosted option is there for teams that need more control over infrastructure, privacy posture, or internal review.

No hosted-only dead end Same core workflow direction Choose based on control, not lock-in

Fastest path to launch

Use hosted ClientShare when you want the workflow without running the infrastructure yourself.

  • We handle the hosted environment
  • Your team gets to value faster
  • Best fit when convenience matters more than deployment control

Most control over deployment

Run the open-source version on your own infrastructure when privacy, hosting location, or operational control matters most.

  • You deploy and maintain the environment
  • You control upgrades and infrastructure choices
  • Best fit when your team wants the most ownership

The product job does not change when the deployment model does.

ClientShare is still about secure client file exchange. The difference is who runs the environment and how much operational control your team needs to keep.

  • Client workspaces for ongoing document exchange
  • Secure links for uploads, reviews, and file delivery
  • Optional client accounts and clear access rules
  • The same core product direction instead of a hosted-only fork
Category
Hosted
Self-hosted
Setup
Start faster with less operational work
Plan, deploy, and own the environment yourself
Maintenance
No self-hosting burden for your team
You manage upgrades, backups, and operations
Control
Simpler day-to-day ownership
More control over privacy, hosting, and access model decisions
Best for
Small firms that want a secure portal now
Teams that want the workflow and their own infrastructure path

Choose hosted when...

  • You want to replace email quickly without taking on infrastructure work.
  • Your team would rather focus on client operations than deployments and upgrades.
  • You want the simplest path to proving whether the workflow fits your firm.

Choose self-hosted when...

  • You have stronger privacy, residency, or internal review requirements.
  • Your team already runs internal systems and prefers to own the environment.
  • You want full deployment control from day one, even if setup takes longer.

Use hosted for speed. Self-host when the requirements demand it.

The point of the open-source path is flexibility, not confusion. Start with the model that fits your team today and keep the workflow consistent as your needs change.