Your app opens inside it, already logged in — and the panels around it do the testing work. And now the same panels can be driven by the agent in your editor.
$79/yr locked for good — first hundredOne email, when it ships. Nothing else.
For testing by hand
A hundred-field form read without a click and filled in one press. A session per tab, so the admin and the customer are on screen together. The finding arrives with the steps already in it.
Manual testing is five applications and a notepad. The app in one window, a second browser for the admin account, dev tools behind it, and a text file where you write the steps down from memory. Jig is one window instead. The page you are testing opens inside it, with your logins already there. It reads the whole form without a click and fills it in one press — and tells you what it left for you to decide. It makes the server fail on demand. You click a flow through once, and a button repeats it after that. Every finding arrives ready to paste into a ticket. Jig — the browser built for QA.
99fields read
1press to fill
3,0svs 72,8 s with Playwright
0scripts written
For QA and for whoever ships the code · macOS, signed and notarised · Windows in progress · everything it measures runs on your machine
The panels
Everything a tester reaches for, in one window.
Pick a panel — the same way you would inside Jig. Each one is a real capture of the product, not a diagram of it.
Fill by set — plausible, the declared limits, what validation must refuse, or everything empty. Lists and consent ticks stay yours, named field by field.
Against how it is done now
Today this is five applications and a notepad.
Nothing here is impossible without Jig. That is the point — it is possible, and it costs a tester their whole day: the browser, its DevTools, a second browser for the second account, an API client, a spreadsheet of test data, and a text file where the steps are being typed up for the ticket.
The way the day goes now
Chrome — the app
your account
Chrome — incognito
the admin account
DevTools
where did that request go?
API client
reproducing the call
steps.txt
for the ticket, from memory
The way it goes in Jig
One press fills the form; it says what it left for you
Every tab is its own session — both accounts on screen
The request is there with its body: copy as curl, send again
Point at the address, press «Fails with 500»
The finding already has the steps, the environment and the response
And it is not an editor. It is the other half of one — now literally.
An IDE is built for the person who writes the code, and every attempt to bolt manual testing onto one ends the same way: a plugin that opens a preview and can tell you nothing about it. Jig starts from the other end — the application is the document, and everything around it is for reading that application rather than editing it. Keep your editor; connect it, and the agent in it gets hands here.
A colour each, and it belongs to the project, not the machine
Five applications open at once and you tell them apart before reading a word: green is staging, red is the production copy nobody may touch. The tint travels with the project — open it on another machine and it looks the same.
Cursor · VS Code · Claude Code
Your agent has never seen the thing it built.
It writes the endpoint, writes the form, and then describes to you what to click — because a coding agent has no browser with your logins in it. Connect your editor to Jig and it stops describing: it opens the page, signs in as one of the project’s roles, fills the form in one pass and reads what the server actually answered.
Two ticks and three lines
In Jig: Settings → Your editor. Off in a fresh install.
Paste the lines it shows into your editor’s MCP settings.
That is it — no port to remember, nothing to keep running.
There is no key in the snippet. Jig writes its address to a file only you can read, and the client picks it up there — so a restart on a different port needs nothing re-pasted.
What it can do from there
Open the page under test, and open it as the admin or the customer
Read the whole form without a click, then fill it in one pass
Read the network with real response bodies, and the console
Make the server answer 500, empty or dead — no branch to deploy
Which project it lands in is decided by the folder your editor is open in; several editors connect at once and none of them moves your window. It is refused for exactly the same reasons the chat here is refused — connecting an editor grants nothing that was not already granted.
Memory
Nobody takes this form apart twice.
The first pass over somebody else’s form costs work: a hand-rolled list of divs has to be pressed, watched, understood — where does the value actually land. Jig does that once and writes it down: a procedure per control, and a whole layer for the form — the order fields take values in, the knots, the places that fought back. From the second pass on it is not analysis any more, it is a read from disk.
How much runs from memory
46%
This machine
22%
Your team
9%
Shared
318
procedures
36
whole forms
+46
this week
3 171
model calls saved
The same three rings Jig shows in its settings, after a week on an internal admin panel.
This machine
Everything worked out here stays with you and runs with no network. The key is the place plus the markup, so the same application is recognised from any of your projects — and a stranger’s site inherits nothing.
Your team
Several machines under one key: what a colleague worked out on your internal admin arrives by itself. Encrypted before it leaves, with a key derived from your licence.
Shared
The first Jig in the world to meet an unknown widget pays for taking it apart — everyone after gets the procedure instantly and free, with no key at all. What travels is a hash and the procedure: no address, no page, no values.
The form was rebuilt — the memory moves with it
A developer adds a field or drops a wizard step: different shape, same address. Jig recognises the form by its place, carries what still applies onto the new structure, and says what changed.
Comment
Due date
Department · Amount · Currency
And twenty-seven libraries it knows with no memory at all
Ant Design, MUI, Vuetify, PrimeReact, Kendo, Mantine, web components — built into the engine, working from the first minute. Memory is for where your own begins: the internal panel built out of divs.
96%of fields filled with no memory and no model — measured across forty pages of forms
What you hand over
A tester is paid for this, not for the clicking.
Not a screenshot and a sentence typed from memory. The finding arrives assembled — steps, environment, the branch and commit under test, and the server’s own answer.
JIG-48121Checkout · order formBlocker
Send stays active while the request is running — a second click double-charges
Steps
Fill the order form · press Send · press it again before the answer arrives
POST /api/orders → 200 REF-48121
POST /api/orders → 200 REF-48122 ← the same order, twice
Everything it measures is local. We would rather say so than claim more.
The browser, the inspector, the form map, the fill, the mocks, the recorder, the audit, the network log — none of it goes anywhere. When you hand a task to Claude, what travels with the question is the shape of the work: the field names of the page, the names of your roles, your checklist and the titles of your findings. What you type stays here, and so do passwords, account logins and the addresses of your stands. A screenshot only ever leaves if you switch that on yourself.
Two rails that do not move
Jig never acts in a tab you are signed into yourself — it works in its own, and the login it uses is the one you gave it. And it only ever opens the sites you allowed for this project; anything else is refused, whatever the task says.
Pricing
Free for everything that measures. Paid for everything that repeats.
The first run of anything is free, always. What you pay for is the second one — because the repeat is where a professional’s time actually goes.
For the person who signs it off
Five testers, the same regression form, every week.
Three seconds in Jig against seventy-three with a Playwright script — and the script had to be written first. Here nobody wrote one.
$149 per seat / year
Invoice from a registered business
Seats reassignable
30-day full trial
Free
$0forever
No account needed
The browser, projects, tabs
A separate session per tab
Inspector and form map
Accessibility audit and Tab-order walk
Network with response bodies, console, curl
Pro
$99/ year, per person
One payment. Nothing renews itself — our till does not keep your card.
Roles — several signed-in people at once
Fill by sets: valid, limits, invalid, empty
Network rules: 500, empty, slow, dead
Record a flow, replay it with a button
Runs, and the difference between two
Claude: hand over a task, ask about a page
Team
$149/ year, per seat
Invoice from a registered business, with the documents your finance department asks for. Seats can be reassigned.
Founding price
$79/ year, fixed for good
The first hundred people to buy keep this price for every year they stay — including after the public price goes up.
A second app, not a discount
Pro comes with QA Copilot
Qiksy QA CopilotChrome extension · already on the Web Store · $49 / year on its own
The same key unlocks Qiksy QA Copilot Pro — our Chrome extension for testing inside the browser you already use. One purchase, both halves of the trade: the browser for the work you plan, the extension for the page you happen to be on.
It rides along in the browser you already have open — your profile, your logins, the tab in front of you. It fills the form, catches the console error, the failed request with the server’s own body and the accessibility violation, and hands the lot back as one file you attach to the ticket. Nothing to script, no second browser to sign into.
Jig is where you sit down to work
A regression pass with a name, several signed-in roles at once, the same form filled four ways, a recorded flow replayed on a button — and the difference between last week’s run and this one. This is the half a lead, a QA owner or whoever signs the release off actually needs: something to show, not a feeling.
QA Copilot is where the page finds you
A developer checking the feature they wrote an hour ago on staging, under their own SSO. Support reproducing what a customer sent. A project manager opening the link in a ticket to see for themselves. Nothing to set up and nothing to plan — it is already in the browser they use all day.
Neither half needs a model to measure. Forms, findings, the network with response bodies, the WCAG audit, the Tab-order walk — local, free, no account and no Claude. A model only enters when you hand the work to an agent, and then it is your own Claude subscription, not tokens resold by us.
So this is not two-for-one. It is one job that happens in two places — the pass you plan, and the page that lands in front of you — and having paid for the larger half, you should not have to buy the smaller one twice. It only runs this way round. A QA Copilot key does not unlock Jig — Jig is the larger tool, and paying for the smaller one cannot buy it.
The trial is a month, not two weeks
Full Pro for thirty days. Two weeks is not long enough to meet a regression, and the regression is the thing Pro is for.
About the model
Connect your own Claude subscription and everything that needs a model is unlimited and costs you nothing extra. Without one, Pro includes a monthly allowance through our cloud — counted separately for each kind of work, so a busy week of one does not eat the others: 300 failure explanations, 200 rule checks, 150 repairs, 150 verdicts, 100 full runs with a plan, 40 checklists and 500 dictations. The run is the expensive one, and it is exactly where your own subscription pays off.
Take the macOS build now.
Leave an address and we will write once — when Windows lands and sales open, with the founding price attached.
Apple Silicon 131 MB · Intel 136 MB — both signed and notarised
Windows: this installer is not signed yet — the certificate is still in identity validation. Windows will show a blue “Windows protected your PC” screen: choose <b>More info</b>, then <b>Run anyway</b>. It installs into your own user profile and never asks for administrator rights. Tested on a real Windows Server 2022: the build behaves exactly as the Mac one.
What happens the first time you open it
You are downloading Jig from us directly, not from a store, so both systems say something the first time. Here is exactly what, and which button to press.
On Windows
The installer puts Jig in your own user folder and never asks for an administrator password.
Windows shows a blue window headed “Windows protected your PC”, and the only button on it says “Don’t run”. Do not stop there. Press the link “More info” first, and a second button appears — “Run anyway”. That is the one you need.
Where that window names the publisher it will say “Unknown publisher”, and that is expected right now: our signing certificate has been bought and is going through the certificate authority’s identity checks. Until it is issued there is nothing to sign the file with. So the name is not what tells you this file is ours — the checksum below does.
On a Mac
The image opens with Jig on the left and a shortcut to Applications on the right: drag the first onto the second, and that is the install.
There are two files, one per processor, and the wrong one will not start. If you do not know which Mac you have: Apple menu, “About This Mac” — the line says either “Apple M…” or “Intel”.
Check that the file is the one we published
Each number below belongs to that exact file. Run the command and compare what it prints with what is written here: if they match, nothing was changed on the way to you.
Signed with our own certificate soonOnce the certificate lands, Windows will show our name instead of “Unknown publisher”. Until then it warns, and the download note says how to get past it.
Signed and notarised by AppleIt opens with a double click — macOS raises no “unidentified developer” wall.
Follow the build
We are building Qiksy in the open — new tools, real progress, the occasional stumble. One short note when something ships.
Qiksy QA CopilotChrome extension · already on the Web Store · $49 / year on its own