Continuity

What happens if Dokus stops.

Written for whoever has to fill in a supplier assessment. What is true today, and what is not yet — both, on one page.

This page was last reviewed on 24 August 2026. It is owned by Artem Kuznetsov, founder of Dokus — continuity decisions are not delegated.

Ownership

Who you are contracting with.

Dokus is operated by Invoid Vision B.V., a Belgian company. It is self-funded: no outside investors, and no plans to sell. Nothing below depends on that staying true, which is the point of writing it down.

Legal name: Invoid Vision B.V.
Enterprise number: KBO/BCE 0777.887.045
Registered seat: Balegemstraat 17/7, 9860 Oosterzele, Belgium
Incorporated: 30 November 2021
Role under GDPR: Controller for account data, processor for the documents you upload
Legal Entity Identifier: Not yet registered — a DORA register entry can use the enterprise number above in the meantime

Leaving

Your records, on the way out.

Export is a standing capability, not a concession granted on exit. It works the same on the day you sign and the day you leave.

Export: One export from inside the product, at any time. No request, no conversation.
Formats: CSV, with the original documents alongside it
Deletion: GDPR erasure, requested at /delete-account
Cost to leave: None. No contract and no cancellation fee on the hosted product

Three situations

What happens in each kind of interruption.

One answer is not honest for all three, so the scenarios are separated: a temporary outage, a planned shutdown, and a sudden failure of the company.

Temporary outage

Backups: Regular backups on a documented rotation. The schedule is in the security description, available on request.
Recovery: Restoration is monitored and practised. Recovery-time and recovery-point targets (RTO/RPO) are agreed in writing for private deployments; for the hosted service they are not published until they can be demonstrably met.
Communication: Outages are communicated by email to affected users. No public status page is operated yet — stated plainly, not softened.

Planned shutdown

Notice: At least 60 days’ notice before a planned closure of the hosted service.
Access: Read-only access continues through the notice period.
Export window: A defined final export window, with records and original documents in bulk.
Peppol: Peppol deregistration and migration support during the notice period.
Deletion: A final deletion schedule, published with the notice.
Support: Support continues through the exit period.

Insolvency or sudden supplier failure

Hosted access: Not guaranteed after an insolvency: there is no mechanism that keeps a hosted service running without the company operating it. This is stated plainly rather than promised.
Private deployments: A private deployment keeps running on the customer’s infrastructure, and source-code escrow is available where the contract requires it.
Your position: Export is a standing capability while the service runs. What you hold outside Dokus is yours.

Supplier assessment

The answers, in the shape you need them.

These are the fields a financial entity has to complete for an ICT provider under DORA. Copy them across.

The answers, in the shape you need them.
Field	Our answer
Substitutability	Our answerSubstitutable. Dokus sits before accounting and is not your system of record; records export in standard formats.
Existence of an exit plan	Our answerYes — this page for the hosted product, and written into the agreement for a private deployment.
Possibility of reintegration	Our answerHosted: records return to your own systems by export. Private: the deployment already runs on your infrastructure.
Impact of discontinuing	Our answerHosted: a planned closure comes with advance notice and a defined export period — see the shutdown scenario. Private: the system keeps running on your hardware — what stops is new releases, not the system.
Alternative providers identified	Our answerYes. Document intake is a competitive market, and your accounting software remains your system of record throughout.
Date of last external audit	Our answerNone to date. An external penetration test is planned before the first private deployment goes live.
Certifications	Our answerNo ISO 27001 or SOC 2 certification. Our security measures are described in full on request, and a data processing agreement is signed as standard.
Notice period	Our answerHosted: cancel at any time; a planned service closure carries at least 60 days’ notice. Private: set in the agreement.
Recovery objectives (RTO / RPO)	Our answerHosted: not published until they can be demonstrably met. Private: set with you and written into the agreement.
Sub-processors	Our answerListed in the privacy policy. One model provider — Anthropic — for the optional Ask assistant only; document reading and classification do not use it.

Escrow

Source code, if a contract requires it.

Dokus is not open-source and there is no downloadable edition, so escrow is the mechanism that answers vendor failure. It is offered rather than pre-arranged: we set it up with an independent agent when a deployment needs it, with release on insolvency or on our ceasing maintenance. Ask during the first conversation and it goes in the agreement.

Asking

Anything not answered here.

Support email is answered within the hour, every day between 08:00 and 20:00 CET, except Belgian public holidays and announced absences. Never later than the same day. Supplier questions — assessments, data processing agreements, security questionnaires — are answered within one working day. Both by the people who build Dokus, not a ticket queue. If the honest answer is that we cannot meet a requirement, that is the answer you will get.

Incidents are communicated by email to affected users. There is no public status page yet.

Talk to the team

This page explains the controls in place today, the commitments we can contractually make, and the safeguards we have not yet implemented.

If the honest answer is that we cannot meet a requirement, that is the answer you will get.