Pro unlocks everything in Free, plus the pieces growing product teams lean on. Here’s how the two plans compare:
| Feature | Free | Pro |
|---|---|---|
| Components | 48 | 180+ |
| Website blocks | 12 | All 140 |
| Figma variables | – | Included |
| SSO and audit logs | – | Included |
An accordion is a stack of headers, each opening a panel of content in place, so a page can list many topics and show only what a reader asks for. Orvain's Accordion family runs to seven: a searchable help page with counted topic tags and a vote per answer, a settings panel of folding sections, and five item shapes, boxed rows for narrow columns, a numbered column for ordered steps, a header card over a body card, a badged row holding a value worth copying, and a minimal item that is only a question until it opens.
The decision readers notice most is whether opening one item closes the rest. Closing them makes two answers impossible to compare, and comparison is exactly why somebody is reading a pricing FAQ, so allow several open unless the items are steps that only make sense one at a time. Scroll is the other thing to get right: opening a panel pushes everything below it down the page, and a reader who clicked one question can end up staring at a different one.
The block under a pricing table answering what the table cannot: billing cycles, changing seat counts, what happens when a trial ends. Several open at once, because people are comparing two answers.
A topic page where search narrows the list and each tag says how many articles sit under it. Answers open beneath their question rather than on a new page, so the result list stays on screen.
Profile, billing and notification sections stacked in one panel, each folding shut once it is done with. A row can hold a switch, or a key with a copy button, without leaving the section.
Numbered steps for connecting a service, opened one at a time. The numbers survive folding, so somebody who stops halfway can still see how much of it is left.
Default to allowing it. Readers open a second item to compare it with the first, and closing the first makes that impossible. Restrict the accordion to one panel at a time only when the content is sequential, such as a setup wizard or a form split into stages, where two steps open together would suggest they can be done in either order.
Not when the answers are in the markup. Render each panel's content into the page and hide it with state the browser understands, rather than fetching it when the header is clicked, and the text is there for a crawler and for the browser's own find-in-page. Give every header a real heading element so the questions keep their place in the document outline.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
An accordion is a stack of headers, each opening a panel of content in place, so a page can list many topics and show only what a reader asks for. Orvain's Accordion family runs to seven: a searchable help page with counted topic tags and a vote per answer, a settings panel of folding sections, and five item shapes, boxed rows for narrow columns, a numbered column for ordered steps, a header card over a body card, a badged row holding a value worth copying, and a minimal item that is only a question until it opens.
The decision readers notice most is whether opening one item closes the rest. Closing them makes two answers impossible to compare, and comparison is exactly why somebody is reading a pricing FAQ, so allow several open unless the items are steps that only make sense one at a time. Scroll is the other thing to get right: opening a panel pushes everything below it down the page, and a reader who clicked one question can end up staring at a different one.
The block under a pricing table answering what the table cannot: billing cycles, changing seat counts, what happens when a trial ends. Several open at once, because people are comparing two answers.
A topic page where search narrows the list and each tag says how many articles sit under it. Answers open beneath their question rather than on a new page, so the result list stays on screen.
Profile, billing and notification sections stacked in one panel, each folding shut once it is done with. A row can hold a switch, or a key with a copy button, without leaving the section.
Numbered steps for connecting a service, opened one at a time. The numbers survive folding, so somebody who stops halfway can still see how much of it is left.
Default to allowing it. Readers open a second item to compare it with the first, and closing the first makes that impossible. Restrict the accordion to one panel at a time only when the content is sequential, such as a setup wizard or a form split into stages, where two steps open together would suggest they can be done in either order.
Not when the answers are in the markup. Render each panel's content into the page and hide it with state the browser understands, rather than fetching it when the header is clicked, and the text is there for a crawler and for the browser's own find-in-page. Give every header a real heading element so the questions keep their place in the document outline.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Search the help centre or browse by topic.
Pro unlocks everything in Free, plus the pieces growing product teams lean on. Here’s how the two plans compare:
| Feature | Free | Pro |
|---|---|---|
| Components | 48 | 180+ |
| Website blocks | 12 | All 140 |
| Figma variables | – | Included |
| SSO and audit logs | – | Included |
Yes. Plans are flexible and there’s no lock-in.
You’re billed for each active member of the workspace, once a month or once a year.
Two-factor authentication takes a minute to set up from your security settings:
Workspaces are hosted in the EU (Frankfurt) by default. Data is encrypted in transit with TLS 1.3 and at rest with AES-256. You can export everything at any time through the API:
curl https://api.orvain.dev/v1/workspace/export \
-H "Authorization: Bearer $ORVAIN_TOKEN"Deleting a workspace removes all of its data within 30 days.
Owners can hand a workspace to another admin without any downtime.
Go to Account → Profile and choose Change email. We send a link to the new address; the change applies once you open it, and your old address gets a heads-up.
No answers for “” yet.
Pro unlocks everything in Free, plus the pieces growing product teams lean on. Here’s how the two plans compare:
| Feature | Free | Pro |
|---|---|---|
| Components | 48 | 180+ |
| Website blocks | 12 | All 140 |
| Figma variables | – | Included |
| SSO and audit logs | – | Included |
Yes. Plans are flexible and there’s no lock-in.
You’re billed for each active member of the workspace, once a month or once a year.
Two-factor authentication takes a minute to set up from your security settings:
Workspaces are hosted in the EU (Frankfurt) by default. Data is encrypted in transit with TLS 1.3 and at rest with AES-256. You can export everything at any time through the API:
curl https://api.orvain.dev/v1/workspace/export \
-H "Authorization: Bearer $ORVAIN_TOKEN"Deleting a workspace removes all of its data within 30 days.
Owners can hand a workspace to another admin without any downtime.
Go to Account → Profile and choose Change email. We send a link to the new address; the change applies once you open it, and your old address gets a heads-up.
No answers for “” yet.
Search the help centre or browse by topic.
Pro unlocks everything in Free, plus the pieces growing product teams lean on. Here’s how the two plans compare:
| Feature | Free | Pro |
|---|---|---|
| Components | 48 | 180+ |
| Website blocks | 12 | All 140 |
| Figma variables | – | Included |
| SSO and audit logs | – | Included |
Yes. Plans are flexible and there’s no lock-in.
You’re billed for each active member of the workspace, once a month or once a year.
Two-factor authentication takes a minute to set up from your security settings:
Workspaces are hosted in the EU (Frankfurt) by default. Data is encrypted in transit with TLS 1.3 and at rest with AES-256. You can export everything at any time through the API:
curl https://api.orvain.dev/v1/workspace/export \
-H "Authorization: Bearer $ORVAIN_TOKEN"Deleting a workspace removes all of its data within 30 days.
Owners can hand a workspace to another admin without any downtime.
Go to Account → Profile and choose Change email. We send a link to the new address; the change applies once you open it, and your old address gets a heads-up.
No answers for “” yet.
Pro unlocks everything in Free, plus the pieces growing product teams lean on. Here’s how the two plans compare:
| Feature | Free | Pro |
|---|---|---|
| Components | 48 | 180+ |
| Website blocks | 12 | All 140 |
| Figma variables | – | Included |
| SSO and audit logs | – | Included |
Yes. Plans are flexible and there’s no lock-in.
You’re billed for each active member of the workspace, once a month or once a year.
Two-factor authentication takes a minute to set up from your security settings:
Workspaces are hosted in the EU (Frankfurt) by default. Data is encrypted in transit with TLS 1.3 and at rest with AES-256. You can export everything at any time through the API:
curl https://api.orvain.dev/v1/workspace/export \
-H "Authorization: Bearer $ORVAIN_TOKEN"Deleting a workspace removes all of its data within 30 days.
Owners can hand a workspace to another admin without any downtime.
Go to Account → Profile and choose Change email. We send a link to the new address; the change applies once you open it, and your old address gets a heads-up.
No answers for “” yet.