Skip to main content

Deployment Planning

AudienceIT Administrators, Infrastructure Teams
Reading Time8 minutes
Use this pageBefore installing the Hub

This page helps you decide what to put where before you run any installers. Once your plan is ready, follow Hub installation, Studio installation, and Runner installation in order.

Before you install

Required

Required

  • A Windows server for the Hub (Server 2019+ or Windows 10/11 Pro)
  • PostgreSQL 14 or later, reachable from the Hub server
  • An HTTPS certificate strategy (operator-supplied certificate or installer-generated self-signed for pilot)
  • Firewall rules allowing the Hub's HTTPS port through to authorized Studio and Runner machines
  • Windows machines for Studio (authoring) and Runner (execution)

Optional

Optional

  • Existing production Redis (otherwise the Hub bundles one)
  • A dedicated database server separate from the Hub host
  • A load balancer in front of multiple Hub instances (Phase 2)
  • Dedicated Runner machines per environment (Development, Staging, Production)

Deployment options

The Hub, PostgreSQL, and Redis can be co-located on a single server for small teams or spread across dedicated servers for enterprise deployments. Both layouts use the same installer; only the connection strings change.

Small team / pilot

Hub, PostgreSQL, and bundled Redis all on a single Windows server. Studio and Runner installed on user workstations. Simplest to operate; suitable for evaluations and small production deployments up to roughly 5 Runners.

Enterprise

Hub on a dedicated application server, PostgreSQL on a dedicated database server (or managed Postgres), production Redis on a hardened cache server. Runners deployed on dedicated execution machines, often per environment. Suitable for regulated deployments, larger Runner fleets, and any installation subject to formal architecture review.

Network considerations

  • The Hub only needs to accept inbound HTTPS from Studio and Runner clients. All other ports can stay closed at the firewall.
  • Runners make outbound HTTPS connections to the Hub. They do not need to accept any inbound connections.
  • Studio communicates with the Hub over HTTPS.
  • Internet access from the Hub is not required for day-to-day operation. Periodic license validation requests reach the Exekra Portal; these can be batched or air-gapped for offline-only deployments.

What to plan next

Was this page helpful?

A quick signal helps us prioritise improvements.