Skip to main content

Ssl certificates hosting — SSL Certificates

This capability is included on every SteboHost plan as standard — not sold as an add-on. This page explains what it does, how it is configured, and the limits that apply, in plain language. The short version: it runs on every account from creation, it is maintained by the team that operates the platform, and its limits are published in numbers rather than adjectives — with real people on '.self::SUPPORT_PHONE.' when you want a straight answer.

Most providers sell this as an add-on because it costs them something to run. The economics here are different: the feature runs on every plan from the moment an account is created, because a protection that only some customers have is eventually a problem for everyone. That is why it is in the base price rather than the upsell list.

Configuration is handled by the platform rather than delegated to you. Where a decision is genuinely yours — a policy threshold, a contact address, a scope — the portal presents it in plain language with the recommended default. Everything else, including the updates you never see, is applied and maintained automatically.

The honest limits are published alongside the capability. Nothing here is described as unlimited, because nothing is: limits are concrete, monitored and enforced consistently, and they are printed next to the feature rather than buried in a footnote.

What's included

  • Included on every plan from account creation — no add-on purchase.
  • Configured and maintained automatically, including updates.
  • Concrete, published limits — no unlimited claims.
  • Monitored continuously with alerts to the team.
  • Documented in plain language, with support reachable on +254 703 610 464.

Good to know

  • Runs on every SteboHost plan from account creation — no configuration step.
  • Monitored continuously from Nairobi; incidents published with reason codes.
  • Included in the base price — not an add-on.

The measurement habit is what turns a capability from a checkbox into a managed asset. The portal reports what the feature is doing, the events it generates are visible rather than hidden, and anything needing a decision arrives in plain language with the recommended response. A protection you can see is a protection you can trust.

The questions worth asking before committing are the ones this page answers directly: what it protects against, what it costs, what the limits are, and who answers when something is flagged. If those four answers are concrete, the rest of the comparison is detail.

The last consideration is the relationship. A provider that publishes its incidents, prints its renewal prices and answers its phone is making itself accountable in ways that are easy to check — which is the standard this page holds itself to.

The honest closing: the capability is part of the platform because the platform is the product. A platform that ships partial protection is shipping a gap, so the protections that matter are standard and the things that vary are the resources.

What that means for the buying decision is simple: the feature is included, the limits are published, and the support team answers on a number a person picks up. Everything else on this page exists to support those three claims.

The practical test for the whole capability is to run it and watch the numbers. The portal reports what it is doing, and the events it generates are visible rather than hidden.

Frequently asked questions

Is this really included in the base price?
Yes — it runs on every plan from account creation, with no setup and no upsell.
Do I need to configure anything?
No. The platform applies and maintains it; the portal shows the current state.
What are the limits?
Concrete and published — this page and the plan pages state the exact numbers rather than the word unlimited.
Can it be turned off?
Some thresholds and policies are yours to adjust in the portal; the core protection is not optional, because partial protection fails everyone.

The practical effect is easiest to describe by what you stop doing. There is no plugin to keep current, no dashboard to check each morning, and no decision to make about when the protection applies. The platform applies the capability to every domain on the account, keeps it current, and surfaces anything that needs a human decision in plain language.

Where the feature intersects with the rest of the platform, the pieces are designed to work together rather than merely coexist. The firewall understands the hosting layer, the backups run before maintenance windows, and the monitoring watches the same services the status page reports. Integration is the reason the feature is part of the platform rather than a bolt-on.

The limits are published because honest limits are more useful than generous-sounding ones. The entry plan states exactly what it includes, the thresholds are enforced consistently, and the portal shows the current usage so a limit is never a surprise. When a workload outgrows one, the upgrade path is a plan change rather than a migration.

The operational detail is where the feature earns its keep. Events are logged with enough context to be useful, thresholds are tuned from live traffic rather than defaults, and the portal surfaces anything that needs a decision in plain language with the recommended response. When something is blocked, cleaned or flagged, the record says what happened and why.

Interaction with the rest of the platform is deliberate rather than incidental. The capability shares its view of the hosting layer with the firewall, runs ahead of the backup schedule so recovery points stay clean, and reports into the same monitoring the status page publishes. That integration is why it belongs in the platform rather than bolted on afterwards.

The scaling story is straightforward: the feature's coverage follows the plan, and the plan pages state exactly where each tier's limits sit. Usage is visible in the portal, so reaching a limit is a decision rather than a discovery. When the workload justifies it, raising the limit is a plan change rather than a migration.

The trust question is best answered by verifiable specifics rather than adjectives. The capability runs from Nairobi on infrastructure whose status is published in real time, the team behind it is the same one that answers the phone, and the platform's ODPC registration and data processing agreement are documented on the compliance page. Those are checkable claims, and they are meant to be.

For visitors comparing providers, the useful question is not whether the feature exists but what happens when it matters. The honest answer here: it runs on every plan from account creation, it is maintained by the team that operates the platform, and its limits are published rather than implied. Everything else on this page exists to support that claim.

If anything in this documentation is unclear, the fastest path to a straight answer is the phone number at the bottom of the page. The team would rather explain a limit honestly than discover it for you later — which is, in the end, the entire brand proposition.

The practical effect is easiest to describe by what you stop doing. There is no plugin to keep current, no dashboard to check each morning, and no decision to make about when the protection applies. The platform applies the capability to every domain on the account, keeps it current, and surfaces anything that needs a human decision in plain language.

Where the feature intersects with the rest of the platform, the pieces are designed to work together rather than merely coexist. The firewall understands the hosting layer, the backups run before maintenance windows, and the monitoring watches the same services the status page reports. Integration is the reason the feature is part of the platform rather than a bolt-on.

The limits are published because honest limits are more useful than generous-sounding ones. The entry plan states exactly what it includes, the thresholds are enforced consistently, and the portal shows the current usage so a limit is never a surprise. When a workload outgrows one, the upgrade path is a plan change rather than a migration.

The operational detail is where the feature earns its keep. Events are logged with enough context to be useful, thresholds are tuned from live traffic rather than defaults, and the portal surfaces anything that needs a decision in plain language with the recommended response. When something is blocked, cleaned or flagged, the record says what happened and why.

Interaction with the rest of the platform is deliberate rather than incidental. The capability shares its view of the hosting layer with the firewall, runs ahead of the backup schedule so recovery points stay clean, and reports into the same monitoring the status page publishes. That integration is why it belongs in the platform rather than bolted on afterwards.

The scaling story is straightforward: the feature's coverage follows the plan, and the plan pages state exactly where each tier's limits sit. Usage is visible in the portal, so reaching a limit is a decision rather than a discovery. When the workload justifies it, raising the limit is a plan change rather than a migration.

The resource question is answered with concrete numbers rather than adjectives. The feature's coverage at each plan tier is published on the plan pages, visible in the portal, and enforced identically for every account. The word unlimited appears nowhere on this site because nothing is unlimited — a limit you can read is a limit you can plan around.

The security posture is layered rather than singular. A web application firewall filters malicious traffic before it reaches the site. Malware scanning runs on a schedule and flags what it finds. Uptime monitoring watches the services customers actually experience, and the results are published rather than claimed. Each layer covers a failure mode the others cannot reach.

The scaling story is straightforward: the feature's coverage follows the plan, and the plan pages state exactly where each tier's limits sit. Usage is visible in the portal, so reaching a limit is a decision rather than a discovery. When the workload justifies it, raising the limit is a plan change rather than a migration.

The trust question is best answered by verifiable specifics rather than adjectives. The capability runs from Nairobi on infrastructure whose status is published in real time, the team behind it is the same one that answers the phone, and the platform's ODPC registration and data processing agreement are documented on the compliance page. Those are checkable claims, and they are meant to be.

For visitors comparing providers, the useful question is not whether the feature exists but what happens when it matters. The honest answer here: it runs on every plan from account creation, it is maintained by the team that operates the platform, and its limits are published rather than implied. Everything else on this page exists to support that claim.

If anything in this documentation is unclear, the fastest path to a straight answer is the phone number at the bottom of the page. The team would rather explain a limit honestly than discover it for you later — which is, in the end, the entire brand proposition.