Partners

We are certified where it matters and neutral everywhere else.

Partnerships are useful when they mean support paths and cost advantages we can pass on. They are harmful when they decide the architecture before anyone has looked at your problem. We hold the first kind and refuse the second.

Platform partners

Where we hold a formal relationship.

Amazon Web Services
Partner network member. Most of what we build runs here, and the relationship gives us escalation paths and credit programmes that reduce your first-year infrastructure cost.
Google Cloud
Partner. Our default where data and machine-learning tooling dominate the workload, and where an existing Workspace estate makes it the sensible ground.
Model providers
We work across the major providers and will run self-hosted models where your data policy requires it. Named in the contract, with retention terms attached, every time.
Everything else
No reseller agreements, no referral commissions, no incentive to recommend one database over another. If we suggest a vendor it is because it fits, and we will tell you what it costs you to leave it later.

Working with us as a partner

Three arrangements, all of them written down.

Agencies and studios

Design and brand studios who need engineering they can put their name on. We work under your brand where you want that, and we will not approach your client directly, in writing.

Consultancies

Strategy and advisory firms who have sold a recommendation and need someone to build it. Fixed scope, fixed price, and a delivery report you can hand to your client unedited.

Software vendors

Product companies needing implementation capacity for enterprise customers, or an integration built properly rather than by the customer’s IT team on a Friday.

Referrals

If you send us work that closes, we pay a referral fee at a rate agreed before the introduction. We disclose it to the client, because a hidden referral is a conflict wearing a courtesy.

Partnership enquiries

Tell us what you sell and where engineering is the constraint. We will say yes or no inside a week.

hello@brilliantsystems.io
Network patch panel with cables connecting numbered ports

Next step

Talk to the engineer who would run your build.

No discovery call with a salesperson, no deck. A senior engineer reads what you send and replies with a real assessment, including when we think you shouldn’t build it.

Tell us what you’re building

We reply within one business day. No sales sequence, no newsletter.

Certified, partnered and awarded