For enterprise
RuleSell for enterprise
Enterprise procurement runs on provenance, not vibes. When an AI coding config is about to enter your codebase, your security and legal teams want three answers: who wrote it, what license governs it, and where it came from. RuleSell ships that today — every listing is attributed to its real GitHub author, tagged with its SPDX license, and linked to its upstream source, with a quality grade on top.
To be just as clear about what is not built: SSO, audit logs, team seats, role-based access, a governance dashboard, SOC 2, and security scanning do not exist yet. They're on the roadmap, and we'd rather have a real conversation about what you need than sell you a feature list we can't back up. RuleSell is free during beta.
The button opens your mail client to founders@rulesell.com — no form, no signup, a real human reads it.
What's usable for procurement today
These are shipped and in production — the provenance and licensing evidence a review actually needs:
Real author attribution
Every listing is credited to its real upstream GitHub author — not an anonymous account — so a config can be traced back to a person and a repository your team can evaluate.
SPDX license tags
Listings carry their SPDX license identifier, so your legal and procurement teams can confirm reuse rights before anything lands in a codebase.
Source provenance
Each listing links to its upstream source, so a reviewer can read the original before it's adopted — provenance you can put in a procurement record.
Quality scoring
An A / B / C grade computed from automated signals (upstream freshness, schema completeness, review signals) gives a defensible first-pass filter instead of gameable star counts.
On the roadmap — not shipped
RoadmapThe classic enterprise checklist below is not built yet. We list it so you know exactly where the gaps are — and so you can tell us which gap to close first.
SSO / SAML
Single sign-on for your identity provider. Not built yet.
Audit logs
A record of who adopted which config and when. Not built yet.
Team seats & roles
Seat-based access with role-based permissions. Not built yet.
Governance dashboard
An org-level view of approved configs and policy. Not built yet.
Help us build the right enterprise offering
We're prioritizing SSO, audit, seats, and license-compliance tooling based on what real teams ask for. Tell us your org size, your tools, and your must-haves — we read every message.
Email founders@rulesell.com →Enterprise — frequently asked
Does RuleSell have SSO, audit logs, or team seats?
No. SSO/SAML, audit logs, team seats, role-based access, and a governance dashboard are not built. We will not list them as features they are not. They are on the roadmap — if any of them is a requirement for you, email founders@rulesell.com and tell us which ones, so we build the ones that actually unblock procurement first.
What can RuleSell actually do for an enterprise today?
The provenance layer. Every config in the catalog is attributed to its real GitHub author, tagged with its SPDX license, linked to its upstream source, and assigned a quality grade. That's the exact evidence procurement and security reviews ask for when a config is going into a codebase — who wrote it, what license governs it, and where it came from. It does not replace your review; it gives that review a real starting point instead of an anonymous gist.
Is RuleSell SOC 2 certified or security-scanned?
No. There is no SOC 2 certification and no security scanning of listings — we do not scan for malware, secrets, or supply-chain risk, and we will not claim we do. 'Verified' on RuleSell means provenance, attribution, licensing, and quality scoring, not a security guarantee. Review any config before you run it, the same as any third-party code.
How do we pay for an enterprise plan?
There is no enterprise plan and no payments today — RuleSell is free during beta, and paid publishing for creators opens after beta. There is no volume licensing or per-seat billing to sign up for. If you want to shape what an enterprise offering should include, the waitlist below is the way in.
How do we get in touch about enterprise needs?
Email founders@rulesell.com (the button on this page pre-fills it). Tell us your org size, the tools your developers use, and which capabilities — SSO, audit, seats, license compliance — would actually unblock you. We're using these conversations to decide what to build first, so specifics help.