Skip to main content

Charter and way of working

Every claim on this page is either checkable on this site or marked unapproved.

Engineering principles

About KaraHub

Why KaraHub exists and how we work.

  • 99.99% Availability written into the contract
  • 100% Data ownership stays with the customer
  • 4 services we run ourselves, with the numbers published

KaraHub started in 2026 (1405) from a simple observation: most small and mid-size Iranian businesses either can't afford a full in-house IT team, or work with scattered freelancers who each see only part of the picture. The result is usually what we named the company after avoiding: technology that isn't in its place: overpriced, insecure, or mismatched to the business's actual size.

For small and mid-size businesses without a dedicated IT team, KaraHub is the technology transformation partner that stays with you from decision to execution.

How we work

Every engagement starts with a defined, time-boxed audit, not an open-ended consulting retainer. You know exactly what you're getting, in what timeframe, and at what cost.

  • Reports are built on numbers and evidence, not generic adjectives.
  • Recommendations are sized to your actual team, not enterprise-scale solutions.
  • Training is part of every project, so your team never depends on us to keep running.

Five commitments

These aren't brochure promises. We hold ourselves to every one of them on every project.

  1. Full documentation. Every project starts with a written scope and is delivered with complete documentation. Your business's technical knowledge never lives in just one person's head.
  2. Honest advice. If a solution isn't cost-effective for you, we say so, even if that means a smaller project, or no project at all.
  3. No lock-in. We build on open-source, standard tools so you're never dependent on us just to keep running.
  4. Transparent commitments. We don't promise what we can't keep; response times and support hours are clear from day one.
  5. Tested recovery. A backup that's never been restore-tested isn't a backup. Every project tests the restore itself, too.

The team

KaraHub is run by specialists with years of infrastructure, security, and data engineering experience across the region, now packaged into defined, measurable services.

Four pillars

Four things we hold to

None of these is a promise. All four can be checked on this site today.

The price is written down

The plans and what the price is based on are published here. "Contact us for pricing" filters for margin, not for accuracy.

See the plans

Pricing model Published on this site

The response time is stated

Every plan carries its own response time, written on the same page. If we cannot keep a commitment we do not make it.

See the response times

Response time Written into every plan

The figures are measured

The status of the services we run ourselves, with real response times, is published — including the times something did not work.

See the status page

Where the figures come from Automated measurement

No lock-in

Your data and configuration are yours and are handed over at the end. The tooling is standard and open wherever it can be.

See how we work

Leaving Data and configuration handed over

The infrastructure as it is

Built for the bad days, not only the good ones

A design written for stable connectivity breaks here on day one. KaraHub’s architecture assumes power cuts, bandwidth that moves, and an international gateway that goes down.

  • Services inside the country keep running when the international gateway drops.
  • Every service has a second copy, and its recovery is rehearsed rather than only documented.
  • Power cuts and bandwidth loss are assumptions in the design, not exceptions to it.

Service availability

12 MEASURED DAYS
  • Website 100.00%
  • Cloud workspace 100.00%
  • Mail service 100.00%
  • Code repository 100.00%
Median response time
74 ms
Services monitored
4
See the status page

How we got here

Where KaraHub started

  1. 2026

    The method is written down

    The five phases, each one's duration, written output and way back were published, so a customer knows what they are getting before they sign.

This chronicle is a placeholder and is not approved yet.

Want an honest look at your current architecture?

The audit starts with a meeting and ends with a document that is yours, whether or not you continue with us.

Request a Consultation