The things the rest of the site raises and does not settle. Every answer below is what CleverHive actually does today — including the ones where the answer is “not yet”.
1 of 3
Using CleverHive today
Can I use CleverHive today?
You can create an account and set up your organization — branches, people, roles and permissions all work. What you cannot do yet is use an application: all 139 are still being built, and none can be bought, installed or tried.
Then why is the catalogue published?
Because what CleverHive is building is worth knowing before it ships, and because a catalogue nobody can see is impossible to give feedback on. Every entry says plainly that it is in development.
When will the free trial open?
When the first application is genuinely finished. A trial of something unbuilt would demonstrate nothing. The free trial page lists what would be eligible, and the count comes from the catalogue rather than from a promise.
What does it cost?
Nothing is for sale yet, so there is no price list. Applications will be bought individually rather than as a bundle, so a business pays for what it uses.
2 of 3
How the platform works
What is the difference between an application and an industry solution?
An application is one capability — point of sale, inventory, payroll. An industry solution is several applications plus the shape of organization they assume. A solution configures; it does not replace. See the three solutions.
What is a branch?
A location you operate from. Applications are switched on branch by branch, and people can be scoped to the ones they work at, so a second outlet is a branch rather than a second subscription. Most businesses start with one.
Do I pay for every member of staff?
A person and a login are two separate things in CleverHive. Most staff — kitchen porters, drivers, shop floor — are in the directory without an account, because they never need to sign in. Only people who use the dashboard need a login.
3 of 3
Access and data
Can somebody give away more access than they have?
No. Nobody can grant a permission they do not hold themselves, and the rule runs inside the same database transaction as the change — so it cannot be skipped by a screen that forgot it, and it cannot be raced by two people editing at once.
If I remove someone’s access, when does it take effect?
On their next request. Permission is recalculated on every call rather than stored in the session, so revoking access does not wait for them to sign out and back in.
Is my data separate from other businesses?
Yes, and it is enforced in the database rather than only in application code. Every table carrying business data is scoped to one organization, and the rules are checked by Postgres itself.
Can I get my data out?
Export is planned and not built. It is named on the reporting page as planned rather than described as though it exists.
Loading