For the CEO, owner or sponsor#
What you are deciding#
Whether to own your web and integration platform (self-hosted, MIT, no per-user or per-call fees) in return for running it yourselves (or paying someone to). It is a good bet if you want control of data, credentials and infrastructure and have, or can buy, the people to run it. It is a poor bet if you need a vendor SLA, certificates or single sign-on today.
Your questions#
| Question | Answer and where |
|---|---|
| What is it, in plain words? | What Whoobe is |
| What will it not do? | Overview, chapter 4: the limits, written first so you can stop early |
| What does it cost? | Overview, chapter 5: what you stop paying, what you start paying, how to compare with your numbers |
| What changes in how we work? | Overview, chapter 6: marketing and IT processes |
| What are the main risks? | Young product (0.1.0), self-hosting responsibility, no outside certificate, vendor risk: overview 7.1 |
| How do we start? | A pilot with one site: overview, chapter 10 |
| What is the evidence behind the claims? | Overview, chapter 8; security status |
| Why is it built this way? | Design decisions: self-hosted and MIT, one workspace per organisation, no engine of our own |
| What can our other systems and apps do with it? | The Client Hub: apps and back-ends use the same integrations and data, without holding third-party secrets |
| Should we support the project? | Why sponsor and contribute |
| Where is the project going, and what is built only if someone funds it? | How Whoobe evolves |
Reading path (about an hour)#
- What Whoobe is (10 minutes).
- Overview, chapters 1, 4, 5, 9 and 10.
- Design decisions, the What it costs part of each.
- Ask your IT manager and security officer to read their pages (IT, security) and report.
Last updated