Questions we get asked
7 questions
Before you ask
Frequently Asked Questions
Answers to common questions about working with KaraHub.
How long does a typical project take?
The remote-work readiness audit runs in a 48-hour window, from the first meeting to the delivered audit document. Cloud migration and automation projects are estimated at 2 to 16 working weeks depending on scope and the size of the organisation; the estimate for each combination is on the Method page. A firm schedule is always given in writing before the work starts.
Do you only work with large companies?
No. KaraHub is built for small and mid-sized businesses. We size the solution to the organisation – from teams of a few people to organisations of a few hundred – rather than heavy enterprise tooling whose maintenance costs outweigh its benefits.
Do you offer support after the project ends?
Yes. Every project includes a defined support period in the contract, with an option to extend on a monthly basis.
How secure is our data during the project?
Access to your systems is scoped strictly to what the project requires, under a clear confidentiality agreement. Details are in our Privacy Policy.
How are costs calculated?
After the initial audit, you receive a fixed-price quote for the defined scope, not an open-ended, unclear hourly rate.
Will your implementation lock us into KaraHub?
No. We build on open-source and industry-standard tools wherever possible, not proprietary, locked platforms. Every implementation ships with full documentation so any technical team can carry on without us.
How do we know our backups are actually restorable?
A backup that's never been restore-tested isn't really a backup. On every project that includes backups, we test and document the restore process itself, not just confirm the scheduled job ran successfully.