Straight answers, no fine-print games.
Everything ops leaders and sellers ask before they trust a marketplace with a break-fix promise. Still unsure? Run the free scan and see the model for yourself.
The guarantee
What exactly does "won't break" cover?
The 90-day break-fix SLA covers in-scope failures of a certified script: a dependency API change, an auth or token rotation, a platform update, or a defect the original scan should have caught. It does not cover changes you make to the script, a third-party service shutting down entirely, or new feature requests. Every listing publishes its exact in-scope and out-of-scope list before you buy — no ambiguity at claim time.
What happens if a script breaks and the seller disappears?
That's precisely what the escrow bond is for. If the seller doesn't deliver the in-scope fix, the 20% bond funds an independent maintainer to repair it. You are never left holding a broken automation with no path forward.
Can I extend the break-fix window beyond 90 days?
Yes. At checkout you can add a 12-month extended SLA for +25% of the listing price. For mission-critical automations that's cheap insurance against a year of platform churn.
The security scan
Is the security scan a guarantee my data is safe?
No scan can promise that, and we won't pretend otherwise. Certification checks for over-permissions, hardcoded secrets, injection surfaces and risky outbound calls, and publishes the findings as a public, auditable scorecard so you can make an informed decision. It substantially raises the floor — it is not a warranty against every possible vulnerability.
How is the break-risk score calculated?
It blends security findings, the number and stability of external dependencies (each scored against a watchlist of deprecation and auth-churn history), execution surfaces, brittleness signals like DOM scraping, and resilience patterns such as retries and error handling. The result is a 0–100 break-risk index and an A–D grade. The free scan runs a lighter version of the same model in your browser.
Does my code get uploaded when I use the free scan?
No. The free break-risk scan runs entirely client-side — your script never leaves the browser. Only the numeric result and your contact details are stored, and only if you submit the optional follow-up form.
Pricing & payments
How does pricing work?
We take 15% of each completed sale. Sellers pay a one-time $99 to certify a script, plus an optional $49/mo Certified Seller plan for unlimited listings and automatic re-scans. Buyers can add a 12-month extended SLA for +25% of the listing price. No listing fees, no per-transaction add-ons. Full pricing →
Why is only a 50% deposit charged at checkout?
For one-time certifications and listing purchases, you pay a 50% deposit today and the balance releases from escrow on badge issuance or once you accept the working automation. It keeps your money tied to delivery. Subscriptions (Certified Seller) bill in full monthly and cancel anytime.
Which payment methods are supported?
Checkout supports card via Stripe, PayPal and Razorpay. In this demo environment the flows are simulated — no card is charged and orders are recorded to your browser only.
Platforms & sellers
What platforms can be certified?
n8n, Make, RPA tools (such as UiPath) and Adobe automations. The scanner detects the artifact type — exported workflow JSON or script source — and scores it against a platform-aware model and dependency watchlist.
I'm a seller — how do I get listed?
Submit your script for the $99 certification, clear any conditions on the scorecard, and post the bond from your first sales. Grade A listings go live immediately. The seller timeline walks through every step from day 0 to bond release at day 90.
Are there any income or earnings guarantees for sellers?
No. We make no income, revenue or sales guarantees of any kind. The Certified badge improves buyer trust, but results depend on your script, pricing and market. All figures on this site are platform pricing, not earnings projections.