SpecViber is in phase 1a: access is by invite. To proceed, request an invite and tell us briefly about the project.
Pricing terms aren't fully published yet. This page is for deciding whether the shared working layer fits how you build, and for requesting an invite if it does.
There's no open self-serve sign-up yet. New users get access through an invite. The fastest path is to submit the access request below and tell us briefly what you want the shared working layer to do better in your project.
If you already hold an invite code, you can register it directly from the navigation above.
Phase 1a is deliberately not instant self-serve. The point is to check fit first, then onboard the right projects with the right next step.
SpecViber fits best when you want to reduce fragmentation between documents, tasks, status, relations, and AI work in a real project.
It tends to fit when you already feel that documents, board, chat, and execution live in too many places — or when you want to start a new project without building the same fragmentation in from the start.
And you want the documents to carry more than just text.
And you want specs and execution to hang together more clearly.
And you want human and agent to work against the same objects.
Not just read a prompt or stare at a disconnected board.
You briefly tell us about the project, how you work today, and where the workflow loses coherence. From there, you get the next relevant step.
The goal isn't a quick form. The goal is a qualified conversation.
Access is invite-only in phase 1a. Tell us briefly about the project and what you want the shared working layer to do better.
Thanks. We'll review your request and come back with the next relevant step.
If your situation is unusual, or if you want to talk about fit before sending an access request, you can contact us directly.
The strongest current public fit is a developer-driven workflow. Team value is there, but as a next layer on top of that foundation.
No. You can reach out whether you want to start right from day one or add the model later.
Describe briefly how the work looks today and where docs, tasks, status, or AI work lose contact with each other.