SpecViber stores only the metadata it needs to coordinate the work — states, relations, assignments, history. Your markdown and your code stay in your project.
That distinction matters for consultants, agencies, and teams working under confidentiality, NDAs, or data-protection obligations. The rest of this page is deliberately precise: where details are public today, they stand clearly; where they haven't been published yet, they're marked as such.
What is clear from current material
SpecViber gives the developer and the AI agent one shared working layer. The shared layer holds metadata that coordinates the work — document properties, checklist and comment states, relations, assignments, history, task information. The markdown content and source code themselves remain on the developer's machine and in the developer's repository.
The agent reads and writes the shared layer through MCP tools, instructions, and skills. It does not require uploading project source code to a SpecViber-hosted service.
Boundary at a glance
Local project content on one side, coordination metadata on the other
The practical boundary is straightforward. SpecViber does not need the project itself to move into a hosted workspace. It coordinates the work by storing metadata around the project, not by taking ownership of the project files.
Stays local: source code, markdown content, repo, IDE session
Shared as metadata: status, checklist states, relations, assignments, history
Agent access happens through MCP tools and instructions, not by uploading the repo
That boundary is what makes the model easier to evaluate for consultants and confidentiality-bound teams.
What is not yet published
Current public material does not yet define pricing-related deployment terms, hosting model, retention policy, subprocessor list, certifications, or exact integration scope. If you need these for evaluation, ask directly.
Pricing-related deployment termsNot yet published
Hosting modelNot yet published
Retention policyNot yet published
Subprocessor listNot yet published
CertificationsNot yet published
Exact integration scopeNot yet published
Need exact answers for evaluation?
If you're reviewing SpecViber for professional use and need exact answers about deployment, data handling, repo access, or privacy — contact us and ask for current status.
