Why Assay

Plain English in. Okta Workflows out.

Cards, error handling, tests and docs take most of a Workflows project. Assay Studio does that work from a sentence, in minutes. Your engineers move from building to reviewing.

Days → minutes

Requirement to first importable version, in our worked example

Designed, priced and drawn in about two minutes; built and graded in one more.

$60

A simple workflow, all in

Design, build, error handling, README, test cases, map and deck. $120 standard, $250 complex; helpers $40.

56

Controls, every time

The review a production estate gets, before you download, not after you deploy.

0

Charged before you decide

Design, diagram and price are free. A build that fails costs nothing.

How it works

AI where judgement helps. Rules where certainty matters.

Between the AI and your export sits a compiler that will not let it guess.

The AI decides

The shape of the automation.

Which flows, helpers and tables it needs, what to ask you first, which trade-offs to name.

The rules decide

Everything that must be exact.

Okta’s import format, every link between flows, Okta’s limits, the 56-control grade and every fix. Same answer every time.

Your engineer decides

Whether it goes live.

That it’s what the business wants, that it passes in a sandbox, and when it’s switched on.

An export file is never sent to a model. A logic review sends an outline of the flow, with the values typed into its cards. Assay does not train any model on what you send. Details are in the privacy policy.

A worked example

One automation, before and after.

“Every weekday at 6:30, find users deactivated the day before, remove each one from every group listed in a Watched Groups table, and record each removal with the time.”

Today

3–4 working days
Requirements and design ½ day
Build: schedule flow, loop helpers, lookups, writes 1–2 days
Error handling and logging ½ day
Tests and documentation ½–1 day
Peer review ~1 day elapsed

With Assay Studio

Under half a day · $140
Describe it, with Studio’s questions 10 min
Design, diagram and price (4 flows) ~2 min
Engineer reads the design 15 min
Build and grade, with the pack 1 min
Engineer tests in a sandbox 1–2 hours

At programme scale: twenty automations, two engineers.

Engineer time

70 → 10 days

About 70 engineer-days today; about 10 with Assay Studio.

For a team of two

7 weeks → 1–2

Seven weeks of building, most of a quarter, becomes one to two weeks.

Build cost

About $2,800

20 × $140. Error handling, tests and docs included in all twenty, to one standard.

Engineer time per automation falls about sevenfold in this example. Workshops and change approval do not shrink, so plan on three to five times the automations in a quarter, not seven.

Assessment

Know what you’re running before it fails.

Upload an export. In about a minute Assay draws the architecture, grades the estate A to E against 56 controls, ranks the fix plan and signs the report.

C

grade

118

open findings

16

failure points

26

item fix plan

The sample estate in the live demo.

See the assessment
Assay assessment fix plan: ranked items with the flows they affect

Deliver the backlog, not just the build.