Pricing and onboarding

Pricing for evidence-backed embroidery digitizing.

DigitizingFlow is in private beta. The first plans define usage limits, onboarding gates, and support boundaries now; self-serve checkout waits until auth enforcement, paid terms, and billing provider setup are complete.

Private beta, sales-assisted onboardingDeferred until paid-launch gates are completeNo plan may convert software_ready_pending_sewout into sewout_approved without physical sewout evidence.

Small shops and first operator pilots

Launch

Private beta

Use the hosted workflow for controlled upload, evidence review, and sewout-packet handoff while product gates are still being validated.

Runs: 50 digitizing runs per month
Uploads: 50 uploads per month, 15 MB per source artwork file
Storage: 5 GB retained artifact storage
Operators: 1 workspace, 2 operators

Included workflow

Artwork intake with source hashes and threat-scan metadata
Queued hosted worker execution for supported runs
PES/DST candidates, reports, previews, and packet ZIP downloads
Manual-review and software-ready-pending-sewout states kept explicit

Launch gates

Auth enforcement enabled for the operator workspace
Privacy and retention policy reviewed for pilot use
At least one synthetic fixture packet reviewed during onboarding

Growing embroidery shops and production teams

Production

Sales assisted

Adds higher run volume, broader team access, and stronger support workflows once billing, legal, and auth cutover gates are complete.

Runs: 250 digitizing runs per month
Uploads: 250 uploads per month, 15 MB per source artwork file
Storage: 50 GB retained artifact storage
Operators: 1 workspace, 10 operators

Included workflow

Admin triage queue for failed, retrying, and manual-review runs
Cost and usage telemetry for storage, compute, AI calls, and failed attempts
Sewout packet workspace for production review handoff
Audit events for sensitive run, retry, note, and packet activity

Launch gates

Approved paid terms, refund/support policy, and pricing
Stripe or equivalent billing provider configured
Authenticated live smoke passed against production

Multi-site operators and regulated production workflows

Enterprise

Custom

Reserved for customers that need security review, data-processing terms, SSO planning, custom retention, or dedicated operational procedures.

Runs: Custom monthly run allowance
Uploads: Custom upload and file-type policy
Storage: Custom retention and offsite backup requirements
Operators: Custom workspaces, roles, and support model

Included workflow

Custom retention, backup, and restore drills
SSO/SAML or SCIM planning before account expansion
Dedicated launch evidence bundle and runbook review
Provider and storage-region review before customer upload volume grows

Launch gates

Security and privacy review complete
Contract, DPA, and support workflow approved
SSO or identity-provider scope decided before onboarding

Billing is intentionally gated

Stripe or equivalent remains unbuilt until prices and terms are approved. Until then, account metadata can model plan status and limits, but there is no live checkout, invoice flow, refund workflow, or customer-facing billing portal.

Plans cannot bypass sewout approval

Every tier keeps generated machine files, software evidence, and physical sewout approval as separate states. The paid-launch path must preserve that product boundary in UI, API, admin, and support procedures.

Onboarding gates

What must be true before paid launch

Private beta access can continue through the launch-access flow, but public paid signup should wait until every required gate has evidence.

Gate	Status	Decision detail
Launch-access request	Ready	The homepage conversion path records pilot interest through the waitlist API and first-party analytics.
Operator auth cutover	Blocked	Production still needs AUTH_BOOTSTRAP_EMAIL and a successful authenticated live smoke before AUTH_REQUIRED=1.
Privacy and retention review	Required before paid launch	The repo has a draft public policy, but paid customer launch still needs legal/privacy approval.
Billing collection	Required before paid launch	Account metadata is billing-ready, but checkout, invoices, tax, refunds, and plan enforcement are not live.
Evidence onboarding	Ready	Synthetic fixture packets and production smoke checks are available for controlled onboarding walkthroughs.

Plan questions

What pricing can honestly claim today

Can I buy DigitizingFlow self-serve today?

No. The current decision is private beta with sales-assisted onboarding until auth enforcement, legal/privacy review, final pricing, and billing provider setup are complete.

Do the plans include production-approved embroidery files?

No plan bypasses the sewout gate. DigitizingFlow can produce software-ready candidates and evidence packets, but production approval still requires physical sewout evidence.

Why are prices not published yet?

The first plans define usage limits and onboarding requirements, but exact dollar prices wait for paid-launch terms, refund policy, and Stripe or equivalent billing setup.

Private beta

Start with a controlled launch-access request.

Early onboarding should review a fixture packet, auth readiness, privacy boundaries, and the software-ready versus sewout-approved gate before any customer upload volume grows.