For security teams: approving Bouraq as a transfer channel

Someone in your organisation asked to use Bouraq. This page tells you what it is, what it is not, and which controls exist today, so you can decide in one review. The technical detail is on the security and architecture page.

See the price and start Watch the proof

€79 / monthbilled yearly (€948), or €99 monthly; 14-day money-back guarantee
≈ 5 kB/s5 MB of logs ≈ 2 min 23 s per loop on a full-HD screen (estimate yours)
Nothing to installone HTML file on the offline PC, and a camera you are allowed to use

What it is, in one paragraph

A downward transfer channel to authorise and log like any other interconnection. Bouraq Prism, an HTML file opened on the isolated PC, encrypts files with a per-account key and shows them as QR codes; a permitted camera reads them into the user's space on our server, which decrypts, checks the sha256 fingerprint and keeps the file for up to 7 days. The way back, if you allow it, goes through the user's private GitHub or GitLab repository or a USB key, and never through our servers.

What it is not

Not a network connection: nothing listens on the isolated PC, no agent, no driver, no executable.
Not end-to-end encrypted today: our server holds each account's key and decrypts to rebuild files. If content must never be readable by a third party, run Bouraq on a server you control.
Not certified: no EAL, CSPN or NATO approval. It does not replace a data diode where your regime requires an approved product.
Not for classified, DR or VS-NfD information, or rooms where cameras are banned.

Controls you can rely on

	Available
Named accounts, sha256 per transfer, time stamps	Every account
Tamper-evident audit trail (hash-chained), CSV or JSON Lines export for your SIEM, kept 365 days	Every instance; exported by the instance administrator
Two-factor authentication (TOTP, RFC 6238)	Every account; can be required for administrators
Approval of each transfer by a second person, with reason; rejection deletes the file	Organisation instance option
Export only: the way back switched off in every issued Prism copy	Organisation instance option
Prism copy fingerprint recorded at issue; key renewal revokes older copies	Every account
Prism CSP default-src 'none'; refuses public or internal repositories	Every copy
Hosting in the EU (Hetzner, Helsinki), retention from configuration	Shared service; your own server on request

Each line is described, with its limits, on the security and architecture page.

A pilot you can sign off

A named sponsor and a handful of users.
Export only at first; the way back as a separate decision later.
Transfer approval switched on, and two-factor authentication required for administrators.
A short list of what users may send, written for them.
Review the audit trail after 30 to 60 days, then decide.

Public sector and regulated organisations

Present Bouraq as a component inside your own approval or accreditation file, never as a product that is approved by itself. For a dedicated instance, an installation on your servers, a purchase order or a bank transfer, write to contact@getbouraq.com.

When to say yes, and when to say no

A good fit

Occasional, human-scale transfers out of restricted but unclassified systems
You want to replace USB exceptions and screen photos with a logged channel
A camera is allowed at the workstation
You can review the trail and revoke an account

Not a fit

Your regime only allows approved or certified products for this flow
Content must never be readable by a third party, and no self-hosted instance
Rooms where cameras are banned
Large or continuous flows

Honest scope. Bouraq is a neutral channel for authorised transfers. It exploits no vulnerability and disables no control; your media, camera and repository policies remain the controls that count. Security and architecture →

Questions

Can a user send anything they like?

Technically, anything they can open on the isolated PC. That is why the controls are accountability and approval: every transfer is tied to a named account and recorded, and on an organisation instance it can wait for a second person's approval before anyone can download it.

Who are the sub-processors?

Hetzner (hosting, Helsinki), Cloudflare (DNS and e-mail routing), Stripe (payment) and Google Workspace (our mailbox). The list and retention periods are in the privacy policy.

How do we check the Prism file before it enters the zone?

Each issued copy's SHA-256 is shown in the user's space and recorded in the audit trail with its key version. Check it with certutil, shasum or sha256sum before carrying the file in.

Review it once, approve it for the people who need it.

See the price and start Security page for approvers

14-day money-back guarantee · €79 a month billed yearly, or €99 monthly.