For large organizations

One test suite for your business teams and your technical teams.

The people who know the process and the people who write the code work in different tools. vikingQA gives them one shared test suite. Business teams describe and click, developers write code, and an AI agent does the QA work for both. You decide who has access, where the data lives and how the tests reach your network.

Talk to salesStart free

Hosted in the EU · GDPR · Your tests stay in your git · SOC 2 Type II and ISO 27001 on the roadmap

Technical teams

Write tests as code, in their own tools.

  • Developers
  • QA engineers
  • Platform
Business teams

Describe a flow, or click through it. No code.

  • Finance
  • Sales
  • Operations
  • Support
The agent

Your AI QA colleague, for both teams.

  • Writes the tests
  • Runs them
  • Heals them
One shared test suitePlain language · Code
  • A manager approves an invoice above the limitinvoice-approval.spec.ts
  • A customer changes the delivery addressdelivery-address.spec.ts
  • A new employee gets the correct accessemployee-access.spec.ts
Control

Access, data and network. Your rules.

01

You decide who can do what.

Roles decide who can do what today. Sign-in through your identity provider, accounts created and removed by your directory, and a record of every action that you can export are on our roadmap.

  • Single sign-on with SAML 2.0 and OIDC. Enforced multi-factor authentication. Roadmap
  • SCIM provisioning and deprovisioning. Roadmap
  • Roles: Owner, Admin, Member and the external Customer role.
  • Custom roles for your own structure. Roadmap
  • Audit log of every action, with export to your SIEM (security information and event management) system. Roadmap
02

Run evidence and configuration are held in the EU.

Your tests are stored in your own code repository, in a standard open format. vikingQA holds run evidence and configuration in the EU. A choice of region and a retention period that you set are on our roadmap.

  • Hosted in the EU: the agent, the database and the file storage.
  • AI model inference runs in the United States by default, under standard contractual clauses.
  • Bring your own model: the agent runs on your own contract with an AI provider. Roadmap
  • A choice of AI model and of inference location for each organization. Roadmap
  • Sandbox execution confirmed in the EU for every payload. Roadmap
  • A US region, for organizations that must keep their run evidence and configuration in the United States. Roadmap
  • Retention period for video, trace and logs set per organization. Roadmap
  • Environment variables and secrets encrypted with AES-256, injected at run time, never written to disk. All traffic encrypted in transit.
03

Reach applications that are not on the public internet.

Test the applications that are not on the public internet, without opening them to it. Run your tests on vikingQA, on your own infrastructure, or both.

  • Fixed-IP egress for each project, for your allow-list.
  • Private runners that run the tests inside your network. Only results leave. Roadmap
  • vikingQA writes to your repository only through pull requests. You decide per project: vikingQA merges them, or a person reviews each one.
Security & trust
For regulated teams

Show what was tested, by whom, with what result.

Every run keeps its evidence, and manual runs carry the name of the tester and their notes. Mapping each test case to its Xray test or Zephyr Scale key, and one exported report for each release with each requirement, its test cases, the result and the evidence, are on our roadmap.

  • Two-way sync with Xray and Zephyr Scale. Roadmap
  • Evidence for every run: video, Playwright trace, network log, console log.
  • Every change to a test is a commit in your git, with an author and a date. With review on, the reviewer is on record too.
See the integrations

How a release sign-off changes.

  • Before: Each team reports quality in its own tool and its own format.
    With vikingQA: One test suite per product, one view of results across teams.
  • Before: Business testers send their results in spreadsheets.
    With vikingQA: Business testers record flows and run test cases by hand. Their results sit next to the automated runs.
  • Before: The audit asks for evidence, and a team rebuilds it from screenshots.
    With vikingQA: The evidence is attached to each run. A release report that you export is on our roadmap.
  • Before: A new tool means a new place where your test assets are locked.
    With vikingQA: Your tests are stored in your own code repository, in a standard open format. If you cancel, every test stays and keeps running.

The whole team contributes. One governed test suite.

DevelopersAdd tests as code.
Business teamClick through a flow, or describe it.
The agentWrites, runs and heals the tests.
One shared test suite6 tests
  • A customer can log in
  • A promo code gives the discount
  • The order confirmation email is sent
  • The invoice shows the correct VAT
  • A password reset works
  • Checkout accepts a saved card
Stored in your own repository
01

Developers

Developers and automation engineers add tests as code. Your own code review rules apply to every test.

For developers: plain Playwright in your repositories, under your branch protection.

02

Business team

Anyone who knows how the application must work contributes with the browser extension or in chat: for example business analysts, product owners, key users, support teams and external testers. The Customer role limits external people to the projects you share.

03

The agent

The vikingQA agent defines test cases, explores the application and writes the automation. It works inside the permissions you set, and its only way into your code is a recorded change (a pull request). You decide per project: vikingQA merges it, or a person reviews and approves it first.

For procurement

The paperwork is ready.

01

Invoice and purchase order

Annual contract, paid by invoice against your purchase order.

02

Data processing agreement

A DPA with standard contractual clauses and a public list of subprocessors.

03

Security review

Your security questionnaire, answered, and an architecture review. A SOC 2 Type II report and an ISO 27001 certificate are on our roadmap.

04

Service level

99.9% uptime SLA. Roadmap

05

Dedicated customer success manager

One named person for your rollout, with a shared channel.

06

Credits for the whole organization

Running your committed Playwright tests costs no AI credits. One pool of AI credits across teams is on our roadmap.

Enterprise plan
RolloutIllustrative

A plan for the first 90 days.

Every rollout is different. This plan is an example; we set the real one with you.

01Day 30

One team, one suite

Single sign-on and roles are configured. The first repository is connected. One pilot team runs its test suite in vikingQA. Roadmap

02Day 60

Business testers contribute

Business analysts and key users record flows and run acceptance tests. Results flow to Xray or Zephyr Scale. Roadmap

03Day 90

Standard for the organization

More teams are onboarded from a template. The first release ships with an exported evidence report. You review the measured results with your customer success manager. Roadmap

Questions from security and procurement.

Where is our data stored, and can we choose the region?

In the EU. AI model inference runs in the United States by default, under standard contractual clauses. A US region and a choice of region are on our roadmap. Your tests are not stored by vikingQA at all: they are files in your own code repository.

Which identity providers do you support?

Single sign-on with SAML 2.0 and OIDC, and SCIM provisioning, are on our roadmap. They cover any provider that supports those standards, such as Microsoft Entra ID, Okta and Google Workspace.

Can vikingQA test applications inside our network?

Yes. Use fixed-IP egress with your allow-list. Private runners that run the tests inside your network are on our roadmap.

What does the AI agent see, and is our data used for training?

The agent sees the application under test, the repository you connect and the knowledge sources you enable for each project. Our model providers, Anthropic and OpenAI, do not train their models on data sent through their commercial APIs.

What happens to our tests if the contract ends?

Nothing. Your tests are stored in your own code repository, in a standard open format. If you cancel, every test stays and keeps running.

Start the security review before the pilot.

A 30-minute call with a founder and the engineer who answers your questionnaire.

Start freeTalk to sales

We build vikingQA with a small group of design partners.Join the design partner program