Cloudflare for SaaS alternative

Managed SSL Certificateson Your Own Servers.

HTTPS for your SaaS customers' domains from one Docker container. RedirHub issues and renews every certificate; traffic never leaves your infrastructure.

your-server-01
$ docker run -d --name tls --restart unless-stopped \    -p 443:443 -v tls-data:/data \    -e REDIRHUB_TOKEN=<your workspace token> \    -e UPSTREAM=http://10.0.0.12:8080 \    ghcr.io/redirhub/self-hosted-tls  ✓ certificates synced · TLS on :443 · proxying to UPSTREAM

Trusted by teams that run their own domains

domains served daily
1M+
requests in the last 24 hours
100M+
platform uptime
99.99%

How it works

TLS ends on your servers. Your application stays where it is.

The container sits in front of your existing application on servers you run. It answers HTTPS for your domains with certificates RedirHub manages, and proxies each request to your application over HTTP.

VisitorsOpen https://your-domain
HTTPS
Your server · the containerOpenResty terminates TLS with the domain's certificate
HTTP
Your applicationUnchanged, at UPSTREAM
edge-sync: Inside the same container, it keeps every server's certificates in step with RedirHub: issued and renewed centrally, pushed to each server, with nothing to copy by hand. Visitor traffic never passes through RedirHub.

Certificates

Issued, renewed and synchronised without a single script on your side

The certificate automation that keeps HTTPS on the 1M+ domains RedirHub redirects every day now serves your servers: the same issuance and renewal, delivered to your infrastructure.

Issued automatically

Add a domain in RedirHub, from the dashboard, the API or Terraform, and its certificate is requested for you, www included. No certbot, no DNS plugins, no cron jobs on your servers.

Renewed before it expires

Renewals run centrally, well ahead of expiry. When something outside our control blocks one, the console and an email say exactly what.

Synchronised to every server

Run the container on up to 100 servers, in any region or cloud. Each one receives the same certificates and picks up a renewal on its own.

Deployment

One container. Two settings.

The image bundles OpenResty for TLS and proxying with edge-sync for certificates. There is no separate dashboard to run and no reverse proxy to configure: domains, certificates and status live in the console you already use.

  1. 1
    Create a tokenIn RedirHub, create a Self-Hosted TLS token for your workspace.
  2. 2
    Run the containerStart it on each server with the token and the address of your application.
  3. 3
    Add your domainsAdd each domain in RedirHub, by hand or through the API or Terraform, and point its DNS at your servers. Certificates arrive by themselves, and renewals follow.
SettingWhat it is
REDIRHUB_TOKENYour workspace's token. It lets the server fetch the certificates of your workspace's domains, and nothing else.
UPSTREAMThe address of your application, for example http://10.0.0.12:8080. Every request goes there once TLS is done.

Wildcard domains

Wildcard certificates with one CNAME record

For *.example.com, point _acme-challenge at the address RedirHub gives you. We answer the DNS challenge from then on, so the wildcard certificate is issued and renewed for good.

TypeNameValue
CNAME_acme-challengeThe address shown in your RedirHub console

One record, set once

The CNAME stays in place. Every renewal after that runs without you.

No DNS credentials to share

Your DNS provider's API keys stay with you: the CNAME only hands the ACME challenge to us.

Every subdomain covered

One certificate for *.example.com, synced to every server running the container.

Why self-hosted

Managed SSL certificates on infrastructure you control

For SaaS platforms serving their customers' domains, and for teams that must keep TLS and traffic on their own infrastructure for compliance, latency or architecture, but would rather not run certificate automation themselves.

Customer-controlled infrastructure

Servers, regions, network and firewall stay yours. TLS terminates on your machines, and requests go straight to your application.

Centralized certificate management

Every domain's certificate and its expiry in one RedirHub console, for all your servers at once.

No ACME automation to maintain

No ACME client, challenge routing or renewal scripts to write, monitor and fix. That work moves out of your stack.

Compared with Cloudflare for SaaS

A self-hosted alternative to Cloudflare for SaaS

Cloudflare for SaaS gives your customers' custom hostnames certificates by routing their traffic through Cloudflare's network. Self-Hosted TLS keeps the managed certificates and moves the TLS endpoint onto servers you run.

Where TLS ends

Cloudflare for SaaS

On Cloudflare's network, in front of your origin.

Self-Hosted TLS

In the container on your own servers.

Where traffic goes

Cloudflare for SaaS

Visitors reach your origin through Cloudflare's proxy.

Self-Hosted TLS

Requests go straight to your application. Neither Cloudflare nor RedirHub sees them.

How it is billed

Cloudflare for SaaS

Per custom hostname, beyond the ones the plan includes.

Self-Hosted TLS

From $219/month with 250 domains and up to 100 servers, and no charge per request, subject to fair use.

Pricing

From $219/mo

250 domains and up to 100 servers included, with the Pro plan

  • 250 domains

    $0.88 /domain

    $219/mo

  • 500 domains

    $0.60 /domain

    $299/mo

  • 1,000 domains

    $0.45 /domain

    $449/mo

  • 2,500 domains

    $0.24 /domain

    $599/mo

  • 5,000 domains

    $0.15 /domain

    $749/mo

  • 10,000 domains

    $0.09 /domain

    $949/mo

  • 25,000 domains

    $0.05 /domain

    $1,349/mo

  • 50,000 domains

    $0.04 /domain

    $1,949/mo

Billed monthly. Up to 100 servers at no extra charge, and no charge per request, subject to fair use. Need more servers? Talk to us about Enterprise.

Get started

Add Self-Hosted TLS to your workspace

Tell us where your servers run. We set it up on your workspace and help you start your first server.

  • From $219/month. 250 domains included, billed monthly.
  • Up to 100 servers. For more, talk to us about Enterprise; pricing is set by contract.
Compare plans
Domains to serve

We use your details only to reply to this request. Privacy policy

FAQ

Questions about Self-Hosted TLS

How do I get started?
Request Self-Hosted TLS on this page. We set it up on your workspace, then you run the container on your servers and point your domains at them. Certificates arrive by themselves.
What are managed SSL certificates?
Certificates whose issuance, renewal and deployment a provider handles for you. With Self-Hosted TLS, RedirHub requests each domain's certificate (www included), renews it well ahead of expiry and syncs it to every server running the container, so you run no ACME client, renewal scripts or cron jobs.
What does it cost?
From $219/month, with 250 domains and up to 100 servers included. More domains follow the volume pricing on this page. There is no charge per request, subject to fair use. For more than 100 servers, Enterprise pricing is set by contract.
Does my traffic pass through RedirHub?
No. TLS terminates inside the container on your server, which proxies each request to your application at UPSTREAM. RedirHub issues and renews the certificates and keeps every server in sync; visitor requests never reach RedirHub.
How is Self-Hosted TLS different from Cloudflare for SaaS?
Cloudflare for SaaS issues certificates for your customers' custom hostnames and routes their traffic through Cloudflare's network to your origin. Self-Hosted TLS also manages the certificate of every domain, but TLS terminates in the container on your own servers, so visitor requests go straight to your application and never pass through Cloudflare or RedirHub. Pricing starts at $219/month with 250 domains and up to 100 servers included, and there is no charge per request, subject to fair use.
Can I add my customers' domains automatically?
Yes. Add each customer domain through the RedirHub API or the official Terraform provider (redirhub/redirhub), the same way you would in the dashboard. Its certificate is issued, www included, and synced to every server running the container, with nothing to do on the servers themselves.
What do I need to run it?
A server with Docker, port 443 reachable from the internet, your workspace token (REDIRHUB_TOKEN) and the address of your application (UPSTREAM). Then point each domain's DNS at your servers.
How many servers can I run it on?
Up to 100 servers, in any region or cloud. Every server receives the same certificates and picks up renewals on its own. For more than 100 servers, talk to us about Enterprise.
Do I still need certbot or another ACME client?
No. Issuance, renewal and the ACME challenges are handled for you. You run no certificate scripts, cron jobs or reverse proxy configuration of your own.

Managed SSL certificates on your own servers, from $219/month.

Get Self-Hosted TLS