Most enterprises can’t produce an accurate list of the services their business actually runs. Not IT services — business services. The ones customers pay for, the ones regulators care about, the ones suppliers are contracted to support. Without that list, every other governance decision floats.
HelixGate is built around the Service Catalogue. It is the authoritative register — owner, tier, lifecycle, dependencies, commercial data — that every other module connects through. The constellation map is the data model.
“Until we had a service catalogue, every change request started with three weeks of asking around. Now it starts with a query.”
§ Head of Architecture, FCA-regulatedStand it up in days, not months. CSV import for first load. Cross-references generated automatically as you add records to other domains.
Owner, tier, lifecycle status, criticality, recovery objectives, commercial data — one record, one truth.
Tier 1 (mission-critical) through Tier 4 (low-impact). Drives RTO/RPO requirements, supplier risk thresholds.
Interactive graph of upstream and downstream service dependencies. Find blast radius before the change.
Self-service import with validation. First load in an afternoon, not a quarter. Mapping templates supplied.
Proposed → live → retiring → retired. EOL dates tracked. Replacement services linked.
Every owner change, tier change, status change — logged immutably. Service ownership is never “just lost”.
Service catalogue is the hub. Every other domain links through it.
An IT service catalogue in the ITIL sense is a list of services available to the business. Useful operationally, but insufficient as a governance foundation. An enterprise service catalogue is something different: an authoritative register of every service the organisation runs, who owns it, what technology and suppliers underpin it, what decisions shaped it, and what risk it carries. That distinction matters when a regulator asks about operational resilience.
FCA PS21/3 requires regulated firms to identify their important business services, map the people, processes, technology, and third parties that support them, and demonstrate that each service can tolerate specified disruption tolerances. That is not a catalogue of available services. It is a governance map of the operational estate — and it needs to be maintained, not just produced once for a regulatory submission.
HelixGate treats the service catalogue as the connective tissue of the platform. Every other module connects through it: suppliers linked to the services they support, contracts attached to the services they govern, architecture decisions linked to the services they shape, business cases traceable to the services they funded. Risk concentration becomes visible when a single Critical supplier underpins three important business services with no contractual exit provision.
Service ownership is explicit. Every service has a named owner, a risk classification, and a dependency map. When ownership changes, the record updates. When a service is retired, the governance history is preserved. The catalogue is a living register, not a slide deck produced for the last audit.
Bring your existing service list as CSV — we’ll show how it imports, how dependencies are inferred, and how the rest of the platform connects.
