Partner program

Deliver projects your clients can test.

Your clients find fewer bugs after go-live, and they see what was tested. Your developers, your functional consultants, the client’s key users and an AI agent build one shared test suite for each client. The suite is stored in the client’s own code repository, so it stays theirs.

For developers: your team pushes plain Playwright. The agent writes and heals tests. Each change is a pull request. You merge it yourself, or you turn on automatic merge and vikingQA merges it for you.

Partner types

Choose the way that fits your business.

Delivery partner: use vikingQA on client projects
For Odoo integrators, development agencies and QA consultancies. You run vikingQA as part of your delivery. Each client gets a project and a test suite in their repository. You show the client what was tested, with evidence, at every release.
Referral partner: introduce a client. We run the demo, onboarding and support.
For consultants, freelancers and agencies that advise on tooling. You introduce a team that needs test automation. We take the first call, the demo and the setup, and we support them after that.
Technology partner: connect your product to the agent
For vendors of test management, issue tracking, CI and business applications. You build an integration so that the agent can read from your product and write to it. We document it together. A listing in the integrations directory is on our roadmap.

What you get.

Every test stays in the client’s git. If the client changes partner, or you stop using vikingQA, the client keeps every test.

BenefitDelivery partnerReferral partnerTechnology partner
One project per clientYes——
Billing per client projectYes Roadmap——
Customer role for your clients’ key users, without a paid seatYes Roadmap——
Free internal workspace for your own teamYes—Sandbox workspace Roadmap
Onboarding and training for your consultantsYesProduct overview sessionTechnical onboarding
Shared channel with the vikingQA teamYes Roadmap—Yes Roadmap
Co-marketing: case study, webinar, eventYes—Yes
Roadmap sessions with the foundersYes—Yes
New integrations and API changes before public releaseYes—Yes
How it works

From application to first client project in three steps.

1. Apply
Send us a partnership inquiry. We reply within two business days and plan a 30-minute call.
2. Set up one real project
We connect one of your client repositories together and train your team on it. Your consultants record their first flows. The agent writes the first tests.
3. Roll out to your clients
You add a project per client. We stay available by email. A shared channel with our team is on our roadmap.

Become a partner.

Tell us about your company: your website, country and team size, which type of partnership interests you, and how your clients test today. We reply within two business days.

  • No fee to join.
  • No minimum number of clients.
  • You talk to a founder in the first call.

Questions, answered.

Does it cost anything to become a partner?

No. The program has no fee and no minimum volume.

Who owns the tests on a client project?

The client. The tests are stored in the client’s own code repository, in a standard open format (plain Playwright).

Can my client’s key users take part?

Yes. They join the client project with the Customer role. They record flows with the browser extension and see the results. A Customer role without a paid seat is on our roadmap.

We are an Odoo integrator. Does vikingQA test custom modules and upgrades?

Yes. The agent tests Odoo in the browser, like a user. You run the same suite before and after an upgrade to see what broke.

We want to build an integration. Where do we start?

Apply as a technology partner. We build the integration with you. Custom MCP servers and a sandbox workspace to test against are on our roadmap.

Catch the next bug before your customers do.

Start free with your own application. No credit card.