How to Choose a Red Hat Reseller for a Provincial Government Department

Choose a Red Hat reseller on six checks: its record in the Red Hat Ecosystem Catalog; fit with your procurement rules; how it handles renewals and co-terming; the certified engineers who would support you; references from comparable public-sector buyers; and a like-for-like quote (same SKU, term, support level and currency). List prices come from Red Hat. Resellers differ on services, support handling, renewal management and currency terms.

The short answer: six checks

Provincial departments usually buy Red Hat subscriptions through a partner, so the real decision is which partner, not which product. The software, the updates and the Red Hat support you receive are the same from any authorized partner. Use these six checks to compare partners:

  1. Verify the partner in the Red Hat Ecosystem Catalog. Confirm the program, designation, specializations and certifications Red Hat itself lists.
  2. Check procurement fit. Make sure the partner can buy through the route your rules require: an existing arrangement, or an open competition under the trade agreements that apply to you.
  3. Separate the licence price from the services. Ask for the subscription quote and any services quote as two separate prices.
  4. Ask how renewals and co-terming are handled. Find out who tracks your renewal dates and how early the work starts before 31 March.
  5. Confirm the certified engineers who would support you. Check named people, their current Red Hat certifications, support hours and the escalation path.
  6. Ask for public-sector references. Speak to a team that bought and deployed the same products.

The rest of this guide explains how to run each check and what evidence to ask for. A scorecard you can copy is near the end.

1. Verify the partner in the Red Hat Ecosystem Catalog

Start with Red Hat's own records, not the partner's website. Red Hat publishes a partner directory in the Red Hat Ecosystem Catalog at catalog.redhat.com/en/partners. Search the company name and open its record. Red Hat maintains the record, not the reseller. A record can show:

  • The partner program and designation, for example a reseller program.
  • The partner tier. Red Hat's partner program has three tiers, which are the same in every region and for every partner type. A partner's tier is set by the engagement points it earns over the year, from activities such as bookings, deal registration, sales and product training, and Red Hat certifications (Red Hat Partner Connect, 28 October 2025). A tier tells you how active the partner is with Red Hat. It does not tell you how good its engineers are in your product area.
  • Red Hat Specialized Partner designations. This is a separate label. Red Hat describes Specialized Partners as partners it has "validated... to provide end-to-end services". The catalog's specialization filters are Mission critical automation, Container management, Virtualization, Application platform, Server/Cloud OS and AI platform (Red Hat Ecosystem Catalog, "Find a partner with the right skills"). A specialization means Red Hat has checked the partner's skills and delivery in that product area.
  • Credentials and certifications. The catalog separates seller credentials, technical seller credentials, and Red Hat Certifications held by technical staff.

What to do with this:

  • Match the specialization to the work. If you are buying Ansible Automation Platform and want help putting it in place, look for Mission critical automation. For OpenShift, look for Container management or Application platform. For moving virtual machines, look for Virtualization.
  • Copy the exact wording from the catalog into your evaluation file. If a partner's website describes its status differently from Red Hat's catalog, ask the partner to explain the difference in writing. The catalog is the record Red Hat maintains.
  • Check the date. Tiers are recalculated every year and specializations can change, so look again just before you award.

2. Check procurement fit

A good partner that cannot buy through your route is not an option. Ask your procurement office two questions first.

Is there an existing arrangement you must or may use? Many provinces and broader public-sector bodies have standing offers, supply arrangements or vendor-of-record lists for software. If one covers Red Hat subscriptions, ask each partner whether it is on it, and ask for the name, number and expiry date. If no arrangement covers the purchase, you will run a competitive process.

Which trade agreements apply? Above certain dollar values, these agreements govern how a provincial purchase must be advertised and evaluated:

  • The Canadian Free Trade Agreement (CFTA). It came into force on 1 July 2017. Its Chapter Five covers government procurement, with a schedule for Canada and for every province and territory (CFTA).
  • The New West Partnership Trade Agreement (NWPTA) for British Columbia, Alberta, Saskatchewan and Manitoba. It has its own procurement chapter, and the four provinces adopted a common bid-protest process in 2019 (Government of Manitoba, 8 February 2019).
  • International agreements such as CETA, and for some buyers the WTO Agreement on Government Procurement and CPTPP, which apply above their own thresholds. Alberta's guidelines on trade-agreement obligations list all of these (Government of Alberta, 2021).

Thresholds differ between agreements and change over time, so take the current figures from your procurement office rather than from any guide, including this one.

Where will the opportunity be posted? In Western Canada, provincial opportunities are posted on:

Ask each partner whether it is registered on the portal you will use and whether it has bid on public-sector Red Hat opportunities in your province before.

3. Separate the licence price from the services

A Red Hat subscription is a defined product: a SKU, a quantity, a term and a support level. List prices come from Red Hat, so for the same SKU, quantity, term and support level the subscription lines should be close. Where quotes differ, look at the discount, the currency and invoicing terms, and what the partner bundles around the subscription.

Services and support handling are different. Design, installation, migration, automation and training vary a great deal between partners in skill, method and price. If they come as one bundled number, you cannot see whether you are paying a low licence price and a high services price, or the reverse.

Ask every bidder for:

  • A subscription quote, line by line, with the currency and invoicing terms stated.
  • A separate services quote, with scope, deliverables, named roles and day rates.
  • The renewal price for each year of a multi-year term, so year two holds no surprises.

If you only need licensing now, say so. You can still ask what services the partner could add later, priced separately.

Ready for a quote?

Tell us what you run and what you need. We will follow up with a quote and the next steps.

4. Ask how renewals and co-terming are handled

Most departments buy Red Hat once and renew it many times, so a partner's renewal handling matters more over five years than a single quote. Provincial fiscal years in Western Canada end on 31 March, and renewals that land in February and March compete with year-end purchasing for the same procurement staff.

Ask each partner:

  • How early do you start a renewal? Ninety days before expiry gives time for quotes, approvals and a purchase order.
  • Can several subscriptions be co-termed to one renewal date, and what does that cost in pro-rated charges?
  • Do you offer multi-year terms, and is the price fixed for the term?
  • How do you handle growth? Find out how added systems or cores are quoted, and whether that happens at renewal or during the term.
  • Do you review support levels at renewal? Some systems may need Premium support (24x7 for Severity 1 and 2 issues) and others Standard (business hours) (Red Hat production support SLA).
  • Who does the department call when something breaks? Product support comes from Red Hat. Find out what, if anything, the partner adds on top.

Our page on Red Hat subscriptions and renewals shows how Unilogik quotes and renews them.

5. Confirm the certified engineers who would support you

If the partner will design, deploy or support anything, you are buying the people. Ask for:

  • Named engineers and their certifications. Common Red Hat certifications include RHCSA, RHCE and RHCA, plus product-specific certifications for OpenShift and Ansible. You can check that a certification is current with its ID on Red Hat Certification Central.
  • The specialization behind the skill. Section 1 shows how to check that Red Hat has validated the partner in your product area.
  • Coverage in your province. Ask where the engineers are based, whether on-site work is included or billed as travel, and what remote delivery looks like. A Vancouver team can serve Regina well, but you should know the model before you sign.
  • Support hours and escalation path. Ask who answers when you call, during which hours, and how a problem is escalated to Red Hat.
  • Continuity. Ask who replaces a named engineer who leaves mid-project.

6. Ask for public-sector references

A useful reference comes from a team like yours: a provincial ministry, a health authority, a crown corporation or a post-secondary institution that bought the same products and used the partner for similar work. Ask the reference:

  • What did the partner deliver, and was it on time and on budget?
  • How were renewals handled in later years?
  • What would you do differently?

Use the reference call to discuss how the partner handles your data and your obligations under provincial privacy law: for example BC's Freedom of Information and Protection of Privacy Act or, in Alberta, the Protection of Privacy Act, which replaced Part 2 of the FOIP Act on 11 June 2025. Your privacy office decides what applies. The question for the partner is practical: which of your systems and data its staff will touch, from where, and under what controls.

Evaluation scorecard

Copy this into your evaluation file and adjust the weights to your policy. The weights are a suggestion for a combined licensing and services purchase. For licensing only, move most of the weight to price and renewal handling.

CriterionSuggested weightEvidence to ask for
Red Hat partner status10%Catalog profile link; program, tier and specializations as Red Hat shows them; date checked
Procurement fit15%Arrangement name, number and expiry, or confirmation of portal registration; prior public-sector bids in your province
Subscription price20%Line-item quote: SKU, quantity, term, support level, currency; renewal price for each year
Services capability and price20%Separate services quote: scope, deliverables, roles, day rates; relevant specialization
Renewal and co-term handling10%Written renewal process; lead time; co-term and multi-year options; how growth is handled
Certified engineers and support15%Named engineers, certification IDs, location and on-site model, support hours, escalation path
Public-sector references10%Two contactable references with similar scope

Where Unilogik fits

Unilogik Systems Inc. is a Vancouver-based IT consultancy founded in 1996. A Red Hat Specialized Partner (RHSP), it implements and supports Red Hat Enterprise Linux, OpenShift and Ansible Automation Platform, and delivers Fortinet security and Dynatrace observability. It serves government, energy and utilities, financial services, healthcare and education organizations across Canada. Quotes in US dollars, Canadian dollars on request. Federal departments can buy Red Hat subscriptions from Unilogik through the federal supply arrangement EN578-232335/078/SMS, which runs to 29 September 2028. Check Unilogik's record in the Red Hat Ecosystem Catalog the way section 1 describes. See Red Hat subscriptions and renewals, RHEL subscriptions for the public sector, the Red Hat partner page, licence assessments, or contact us.

FAQ

Look the company up in the Red Hat Ecosystem Catalog (catalog.redhat.com, Partners). The record shows the partner program, designation, specializations and certifications. Red Hat maintains it, not the reseller. Compare it with what the reseller says on its own site.

Ask for the exact partner program and designation; the named Red Hat certifications held by the engineers who would support you; currency and invoicing terms; support hours and escalation path; how renewals are tracked; and references from comparable public-sector buyers.

List prices for Red Hat subscriptions come from Red Hat. Resellers differ on bundled services, support quality and currency terms. Compare the total quote, including support and renewal handling, not only the subscription line.

The Canadian Free Trade Agreement applies to all provinces. BC, Alberta, Saskatchewan and Manitoba also apply the New West Partnership Trade Agreement, and CETA applies above its thresholds. Thresholds change, so check your procurement office's current figures.

Often, yes. One partner for both shortens the path from purchase to a working platform and gives you one accountable contact. Price the two separately so you can compare them.

Unilogik Systems Inc. is a Vancouver-based Red Hat Specialized Partner (RHSP), founded in 1996. It quotes Red Hat subscriptions for Canadian public-sector buyers and also implements OpenShift and Ansible.

Sources (checked 2026-11-03)

Ready for a quote?

Tell us what you run and what you need. We will follow up with a quote and the next steps.