01
Define
Turn the requirement into clear rules
A legal or compliance expert defines what to ask, which conditions apply, and what should happen. The visual builder keeps the reasoning readable.
Turn legal rules
into action.
A legal or compliance expert defines what to ask, which conditions apply, and what should happen. Your team reuses that work—and gets a versioned audit record every time.
Clear questions and rulesReusable workflowsVersioned evidence
A simple example
A customer triggers a risk flag →The team answers the relevant questions →The published rules determine the next step →ProseID keeps the evidence
How it works
Define it once.
Use it again and again.
ProseID calls the reusable set of questions, conditions, and outcomes a schema. Create it once, publish a fixed version, then let people use it consistently.
02
Publish
Freeze a trusted version
Publish a version that cannot be silently rewritten. When the law or interpretation changes, release a new version without changing earlier results.
03
Use
Let people apply it consistently
Run the rules as a form, guided assessment, determination, or checklist. Every completion records the answers, result, and exact version used.
One set of rules · four ways to use it
Choose the experience that fits the work.
A Flow is the screen a person actually uses. The same published schema can power a form, guided assessment, calculated decision, or checklist without rebuilding the rules.
Standard form
Collect the complete set of facts in one responsive document.
Guided assessment
Reveal one relevant question at a time as earlier answers change the path.
Determination
Turn a known set of facts into a calculated, reviewable outcome.
Compliance checklist
Review explicit controls and retain the completed check as auditable evidence.
What ProseID keeps track of
Every result stays tied
to the rules behind it.
See who created the interpretation, which version was used, what answers were given, and why the result followed.
Published versions stay fixed, so every result remains tied to the interpretation that produced it.
Questions, conditions, exceptions, and outcomes turn written requirements into a process people can follow.
Use the same rules as a form, guided path, calculated outcome, or auditable checklist.
Every public version shows who published it, what changed, and which version a business has chosen to use.
See it in action
Define the rule.
Preview what people will see.
Build readable decision rules on the left. See the questions, outcome, and validation on the right.
Decision logic
R—001
When risk_level is high
Require enhanced_review is complete
R—002
When owner_verified is no
Require onboarding is paused
Customer due diligence
Answer the facts used to decide the required level of review.
Customer risk level
High ⌄
Enhanced review completed
Yes ✓
Enhanced review confirmedThe answers satisfy the published rule.
One connected system
Everything needed
to reuse a rule safely.
Visual builder01
Turn expertise into visible rules
Questions, conditions, and validation stay in one readable workspace. The visual builder and JSON editor always describe the same interpretation.
Versioned releases02
History stays true
A workflow can follow the latest release or stay attached to an exact version. Published versions never change.
Flow experiences03
Use the right format for the work
Present one published version as a form, guided assessment, determination, or checklist without rebuilding its rules.
Open registry04
Start from work that already exists
Find published interpretations, see who created them, and adopt a specific version instead of beginning again from legal prose.
Public registry
Find trusted work before
starting from scratch.
Legal and compliance experts can publish reusable interpretations. See who created them, inspect what changed, and choose the exact version your workflow will use. Verified publishers can optionally earn when another business completes a Flow built from their work.
Explore published interpretations ↗Illustrative registry preview
SchemaReleaseStatus
Data request intakePrivacy · access workflowv2.1.0Published
Customer due diligenceKYC · individualv1.4.2Published
Employee onboardingEmployment · generalv1.0.0Example
Simple usage pricing
Pay when work is completed,
not for seats.
A completed form, assessment, determination, or checklist uses one credit when it creates its audit record. Unfinished attempts cost nothing. A registry schema may carry a clearly shown publisher add-on.
Free
$0forever
50 signup credits
- Hosted workflows
- Versioned records
- Automatic result delivery
Lite
$20per month
100 monthly credits
- Hosted workflows + API
- Automatic result delivery
- Top up at any time
Most useful to start
Starter
$50per month
250 monthly credits
- Hosted workflows + API
- Duplicate-safe records
- Volume top-ups
Growth
$200per month
1,000 monthly credits
- Priority delivery
- Separate API keys
- Email support
No subscription required
Top up when you need more.
Top-up credits never expire. Larger top-ups receive a volume bonus, shown before you buy.
250credits
+0 bonus +0%
$5 top-ups above $200 earn a volume bonus — up to +30% at $500+ $10,000
Questions, answered
The details that
matter first.
What problem does ProseID solve?+
Legal requirements are written in prose. Businesses repeatedly turn that prose into questions, decision rules, forms, and checks—often rebuilding the same work. ProseID lets an expert create the interpretation once, publish it safely, and let other teams apply it consistently.
What is a compliance schema?+
It is the reusable set of questions, conditions, outcomes, and checks behind a compliance process. ProseID keeps each published version fixed so later changes never rewrite earlier results.
What is a Flow?+
A Flow is the experience a person actually uses. The same published rules can appear as a form, guided assessment, determination, or checklist without being rebuilt four different ways.
Does ProseID sign records?+
No. The respondent can add a basic typed-name electronic signature. ProseID hosts, validates, and records the ceremony but never presents itself as the signer.
What happens when a schema changes?+
A published version never changes. A new release can become the latest version, while earlier records remain tied to the version they actually used.
When does a Flow use a credit?+
Only when it completes and creates a record. Starting or abandoning a Flow does not consume a credit.
Turn one requirement into something people can use.