Help center
Help & docs
Everything you need to understand Rough — what it is, how it works, and how different teams get value from it.
Rough lets SaaS customers extend a product themselves — building lightweight features on top of it, without code changes from the vendor. These docs explain the moving parts, show how Rough fits into a product, and break down how each kind of team uses it day to day.
This is a starter set of pages. We'll keep adding to it. If something's missing or unclear, email us at hello@rough.app.
Start here
What is Rough?
The high-level pitch — what Rough is, who it's for, and the problem it solves.
Features
What a Rough Feature is, what it can do, what it can't, and the most common questions.
How RAF works
The architectural pattern that makes Rough Features safe to embed in a host product.
Security
How Rough handles isolation, data, and access — described from how the system actually behaves.
For your team
Product teams
Protect the roadmap, learn from real demand, and absorb edge cases without derailing focus.
Engineering teams
Where Rough fits in your stack, what you have to build, and the safety guarantees you keep.
Sales teams
Close deals you'd otherwise lose to feature gaps. Customisation as a live differentiator.
Customer Success
Resolve customer requests without filing a ticket. Hand customers the tools they need.
End users
If you're using a product that's powered by Rough, here's what's happening and what to expect.
Looking for something else?
For pricing, see the pricing page. For a live walkthrough, visit the demo. To talk to a human, get in touch.