Pricing
Every voix engagement is a one-time project fee. A documentation migration is quoted after a scope review; there is no subscription, no per-seat charge and no platform licence to renew. Once your documentation is in your own Git repository, keeping it there costs nothing.
One-time fee per project. No subscription and no per-seat cost.
50% at signing, 50% on delivery, both set in a written proposal.
Two business weeks from the deposit and the materials the work needs.
Three price points
There are three things you can buy. One of them is the migration itself; the other two are optional and sit on top of it.
Custom quote
A one-time fee, scoped by documentation volume, complexity and implementation requirements. It covers the whole engagement — audit, architecture, implementation, training and handoff — and ends with your team publishing without voix in the loop.
Small extra cost
Five post-launch maintenance interventions for fixes and minor updates, bought on top of the migration. Worth taking if your team wants a safety net while it takes over authoring.
500 EUR
A one-time build, available on request and scoped separately from a migration. It is the one price on this page that does not need a scope review first.
One-time means one-time. voix does not sell a subscription, a per-seat licence or a hosting plan, and nothing here renews. What you end up with is an open-source stack running on infrastructure you control, so the cost of keeping the documentation online after handoff is whatever your own hosting already costs. Whatever is agreed goes into a written proposal before work starts.
Scoping
Two documentation sets with the same page count can be weeks apart in effort. These are the variables that move the number, and the ones you will be asked about first.
None of these is padding. Each one maps to hours inside a phase you can see in advance: the engagement process lists the phases in order and says who does what in each of them. If your setup has an awkward edge — a docs site that is half marketing pages, a translation workflow, an API reference generated from source — the FAQ covers the ones that come up most.
Delivery scope
The migration fee buys a finished engagement, not a content dump into a new repository. Scope is confirmed per project in the proposal, and these are the standard building blocks.
Each block is described in depth on the services page, including what voix does not take on. Anything not written into the proposal is out of scope until it is approved in writing, which is what keeps the one-time fee a one-time fee.
Commercial terms
Every engagement runs under a written proposal or statement of work that fixes scope, timeline and fees before anyone starts. This is the short version of what that document says about money.
This is a summary, not the agreement, and it adds nothing to it. Late payment, the limits on liability, and the governing law of the Republic of Moldova are all set out in full in the terms and conditions. How your material is handled while the work runs — who can see it, how long a copy is kept, what happens when you ask for it back — is covered separately in the confidentiality policy.
Straight answer
A documentation migration from voix is a single one-time project fee, quoted after a scope review rather than published as a list price, because the cost is driven by how much of your content has to be rewritten rather than converted and that cannot be read off a page count.
A single published price would be wrong in both directions: too high for a small product manual that exports cleanly, far too low for a platform reference spread across three systems where half the pages need rewriting before they can move. Quoting per project keeps the fee tied to the work rather than to a tier someone picked off a page.
What comes back is a written proposal with scope, timeline and fee — the same document the engagement then runs under. Nothing starts before it is signed and the deposit is received, and the fee does not move afterwards unless you approve a change in writing.
If you would rather see the shape of the work before asking for a number, the services page describes what is delivered and the FAQ answers the questions that usually come before a first email.
Describe what you have and where it lives today. You get back a written proposal with scope, timeline and a one-time price.