Skip to content
vFileLock powered by VOIMARvFileLock powered by VOIMAR

Deployment models

vFileLock is not locked to VOIMAR's own systems. Choose how it reaches your people.

Livewith planned items markedPlanned
Live

Hosted by VOIMAR

Your organisation as its own tenant on VOIMAR's network in South Africa
  • Runs on VOIMAR's own network in South Africa. No foreign cloud.
  • Your organisation is its own tenant. Every file, record, policy, key and setting belongs to one tenant, and nothing reads across tenants. A file of another organisation simply does not exist for you.
  • Your own clearance and role groups, your own Information Officer and approvers, your own recovery choice.
More on this model
Livewebhooks planned

Enterprise overlay

vFileLock laid over the applications you already run, through an API and a connector
  • Register a document kept in your own system. No file reaches VOIMAR. It gets a level, an owner and its own hash chain.
  • Ask before acting: "may this person open, share, download, print or export this document?" The answer is yes, no, or needs approval, with the rules the level forces. Every no is recorded by vFileLock itself, so your system cannot forget a refusal.
  • Write what your system did into the document's chain, for example printed or moved.
More on this model
Planned

In your own network

The same software installed inside your data centre or private network
  • One container image with only the modules you license, a reverse proxy (yours or ours), a database and a storage volume for locked files.
  • A documented settings file. Secrets are named there and kept in your own secret store, never in the file.
  • Versioned database changes, run at start, always after a backup. Upgrade: new image, backup, migrate, health check. Rollback: the previous image and the backup.
More on this model

1. Hosted by VOIMAR

  • Runs on VOIMAR's own network in South Africa. No foreign cloud.
  • Your organisation is its own tenant. Every file, record, policy, key and setting belongs to one tenant, and nothing reads across tenants. A file of another organisation simply does not exist for you.
  • Your own clearance and role groups, your own Information Officer and approvers, your own recovery choice.
  • People sign in with Voimar ID. Recipients outside your organisation need no account.

2. Enterprise overlay: middleware over your own applications

Your document system, HR system, case system or intranet keeps its files. vFileLock adds three things around them: the classification, the decision about who may do what, and the record.

A versioned API Live

The classification and record service has a versioned REST API, /custody/api/v1.

  • Register a document kept in your own system. No file reaches VOIMAR. It gets a level, an owner and its own hash chain.
  • Ask before acting: "may this person open, share, download, print or export this document?" The answer is yes, no, or needs approval, with the rules the level forces. Every no is recorded by vFileLock itself, so your system cannot forget a refusal.
  • Write what your system did into the document's chain, for example printed or moved.
  • Read and verify the ledger, and export the policy as JSON.

Keys and safety:

  • Each organisation makes its own caller keys, with scopes: classify, check, record, read the ledger, read the policy, share status. A key is shown once, stored only as a hash, tied to one organisation and to your systems' addresses, and can be revoked. Every use is recorded with the key's name.
  • When a person is behind a call, your system passes that person's sign-in token. vFileLock reads their groups itself, so no system can claim a clearance on someone's behalf.
  • No key can make or open a share, receive a key half or touch recovery. Those happen only in a person's browser.
  • A retried request is applied once: requests can carry an idempotency key. Within version 1, fields may be added but nothing is renamed or removed. A breaking change becomes version 2.

The connector Live

Your web application opens vFileLock's page in a small window and hands it the file. The level, the rules, the policy check, the codes and all the encryption stay on vFileLock. Your application gets back the link and the share's status. It never sees a key half or a code. Only the web addresses your organisation lists may use the connector, matched exactly.

Planned signed webhooks

Every event in the record, sent to the endpoints your organisation chooses: signed with HMAC-SHA256 over the time and the body with your own secret, refused if replayed, retried from 1 minute to 24 hours, with a delivery log and a redeliver button.

Planned bring your own identity and record

  • Your systems sign in with standard OIDC client credentials.
  • In your own install, people sign in through your own OIDC identity provider.
  • The record can also flow to a GDPR register or a security monitoring system.

The middleware pattern, step by step

  1. A person in your document system presses Share.
  2. Your system asks vFileLock, with the person's token: may this person share this document with this recipient?
  3. vFileLock answers needs approval, with the forced rules, and records the question.
  4. Your system opens the connector, or raises the approval request.
  5. The approver decides

    The share goes live or ends.
  6. Every step is in the document's chain, and in your Information Officer's view.

The same doors for VOIMAR's own platforms

vKONNECTOR, vKOM-SECURE, vCOMMANDER, the Repo and the Record Store are built to use the same connector and API that your systems use. Today a vFileLock link can be sent in a message in VOIMAR's communications apps.
Coming the share screen inside the apps, the Repo actions and the Record Store. See vFileLock with vKOM and UCC.

3. In your own network Planned

  • One container image with only the modules you license, a reverse proxy (yours or ours), a database and a storage volume for locked files.
  • A documented settings file. Secrets are named there and kept in your own secret store, never in the file.
  • Versioned database changes, run at start, always after a backup. Upgrade: new image, backup, migrate, health check. Rollback: the previous image and the backup.
  • A container compose file first, a Kubernetes package later.
  • No call home. No telemetry, no licence check over the internet, no outside fonts or scripts. It talks only to your own sign-in, mail, SMS, compliance record, webhook endpoints and vault.
  • With key escrow, your recovery key is held in your own vault.

Open standards, no lock-in

Files are standard OpenPGP. The ledger exports as CSV and JSON with the chain proof. The policy exports as JSON. If you ever leave, your files and your evidence leave with you.

See vFileLock with your own files and rules

Bring your Information Officer, your security officer and your IT lead. Or open vFileLock and lock your first file.