Skip to content

Security and trust

Your books deserve the infrastructure a bank would use.

Your company gets its own database, encrypted and backed up.

AWS · FrankfurtIts own databaseEvery change fingerprinted
Your company
Your company

Your company’s own database, encrypted and backed up. Example companies.

Powered by AWS

Amazon Web Services, Frankfurt (eu-central-1), in the EU.

The old way

Books on a laptop are one spilt coffee away.

Spreadsheets, emailed PDFs and a backup someone forgot. That way of keeping books made sense once. It doesn’t now.

Encryption and infrastructure

From your screen to Frankfurt, and back.

Encrypted on the way, guarded at the door, locked at rest.

Our private network in Frankfurt

Memory cache

Amazon ElastiCache

Your browser

Encrypted on the way

TLS 1.2 or 1.3

Front door

Filters known attacks

AWS WAF

Cybooks app

Runs in two data centres

AWS Lambda, serverless

Background work

Imports, documents, the Brain

Amazon SQS, encrypted

Your database

Your company’s own

Amazon Aurora, encrypted

Your documents

In your company’s folder

Amazon S3, AES-256

Backups

Up to 35 days of recovery

Point-in-time recovery

No public address

  1. Your browser

    Encrypted on the way

  2. Front door

    Filters known attacks

  3. Our private network in Frankfurt

    Cybooks app

    Runs in two data centres

    Your database

    Your company’s own

    Memory cache · no public address

  4. Background work

    Imports, documents, the Brain

  5. Your documents

    In your company’s folder

  6. Backups

    Up to 35 days of recovery

Your books live in a private network in Frankfurt. Your database has no public address, so the internet can’t reach it directly.

Encrypted on the way. Every connection uses TLS 1.2 or 1.3, and plain http is turned away to https.

Guarded at the door. A web application firewall with AWS’s managed rules against SQL injection, known bad inputs, bad addresses, bots and account takeover.

Locked at rest. Your database and its backups are encrypted with keys managed in AWS KMS, your documents with AES-256, and secrets such as bank credentials a second time.

A database per company

Every company gets a database of its own.

Not a row in a shared table. A separate database, yours.

Olive & Thyme
Limassol Marine
Your company
Nicosia Code Labs
New company
Olive & ThymeInvoice INV-3211€1.240,00
Your companyBill BILL-0366€14.200,00
Limassol MarineBank line−€380,00
Nicosia Code LabsInvoice INV-0042€3.600,00
Your companyBank line−€1.126,40
Olive & ThymeBank line€612,00
Limassol MarineBill€2.960,00
Your companyInvoice INV-0142€4.180,00
Olive & Thyme
Limassol Marine
Your company
Nicosia Code Labs
New company

One database per company. Example companies.

  • Its own database

    Created for your company when it signs up, and deleted with it.

  • Its own folder

    Your documents under your company’s own folder, served through short-lived links.

  • Its own search

    In-app search keeps a separate index for each company.

  • Its own cache

    Data kept in memory for speed is kept apart for each company.

Serverless and auto-scaling

It grows when the work arrives, then rests.

The app runs serverless on AWS, as many copies as the moment needs. The database is Amazon Aurora, and it grows on its own across a 256-fold range. Nobody adds a server.

The database’s capacity, every four hours

Measured on our live systems, Thu 1 to Thu 15 Oct 2026. The line: the average in each four hours; the band: up to its highest.

128 · the ceiling, room it can still grow into

27,5 · the busiest moment, Sun 11 Oct

0,5 · at rest

0,5 to 27,5

the database at rest, and at its busiest moment

4×

more than four times that peak, still free above it

362

copies of Cybooks working side by side at the busiest moment

Capacity in Aurora capacity units, log scale. “Copies” counts the app’s serverless copies across our platform at the busiest moment.

Backups and recovery

Made a mistake? We can turn back the clock.

Up to 35 days of recovery. Old file versions for 90.

Point-in-time recovery · up to 35 days

Restore to Fri 9 Oct, 09:41

Wed 30 SepNow · Thu 15 Oct, 09:41

An illustration: drag to pick a moment.

  • Up to 35 days back

    The database keeps a continuous record, so we can restore your books to a moment within the available backup history, up to 35 days.

  • 90 days of versions

    Replace or delete a document by mistake, and its earlier version is kept for 90 days.

  • Protected from deletion

    The production database can’t be deleted by accident.

The audit trail

Every change in your books has a fingerprint.

Who did what, and when. Each entry is stamped with a SHA‑256 fingerprint, and the database itself refuses to edit or delete it.

Roles, permissions and two-factor sign-in

You decide who sees what and how they sign in.

Roles for every job, and two-factor for the whole company. Give your accountant the books; keep the settings to yourself.

Example company
Roles and permissions
AreaViewCreateEditDeleteApprove
Bank accounts
Bills
Invoices
VAT returns
Payroll
Reports
Lock periods
Users and settings

Sign-in rules

Two-factor for everyone

OptionalWithin a weekFrom today

NANorthlight Accountants LtdAccountant

Invited Tue 13 Oct · link ends Tue 20 Oct

Two-factorWhen they join

The second factor is checked on every way in
Roles and permissionsAccountant
AreaViewCreateEditDelete
Bank accounts
Bills
Reports
Users and settings
Two-factor for everyone · From today

The Cybooks Brain

The Brain works for you, and never around you.

It proposes, you decide, and it never moves money.

Your decisions on bank lines47 of 50 so far

Auto opens at 50, only when even a cautious count says it’s right at least 9 times in 10. One wrong automatic booking locks it again.

  • It never moves money

    It can’t make a payment, and your bank connection is read-only.

  • Checked like a person

    Before anything is booked, our servers check its proposal the same way they check yours.

  • It learns from you

    Only a person’s correction teaches it, company by company. We test it against examples people have checked.

Monitoring

Watched around the clock, with alerts in minutes.

Every admin action recorded. Threat detection that never sleeps.

Our AWS account, last night

An example alert

Security inbox

Threat detection · a serious finding

03:12 · within a minute, in our own test

Sent to our security inbox

Each point is an administrative action, recorded. At 03:12 threat detection flags one, and the alert reaches our security inbox.

  • Every admin action, recorded

    In every region of our AWS account, kept for a year, in log files that show if anyone altered them.

  • Threat detection that never sleeps

    It watches the account day and night. A serious finding reaches our security inbox within minutes.

  • Our team, on two-factor in Cybooks

    Every Cybooks staff account in the app must sign in with two-factor.

ISO/IEC 27001

We’re putting ourselves through ISO/IEC 27001.

The international standard for running information security. We started in September 2026. We’re not certified yet; when we are, this page will show the certificate.

September 2026

Started

Our scope, risks and controls written down; our policies drafted.

January 2027

Internal audit

An internal audit against the standard.

February to March 2027

Certification audit

By an accredited certification body.

Then

The certificate

Shown on this page, with its number.

We are here · October 2026

What we don’t have yet: an ISO/IEC 27001 certificate, a SOC 2 report, an independent penetration test and single sign-on for your company. We’d rather show you the controls we run than a badge we don’t hold.

The cover of the Cybooks security paper: How Cybooks protects your company’s books

Security paper

For your IT reviewer: the full security paper.

Every control in plain words, and what we don’t do yet.

  1. How Cybooks is builtp. 4
  2. Keeping each company apartp. 6
  3. Encryptionp. 7
  4. Backups and recoveryp. 8
  5. Sign-in and accessp. 9
  6. The audit trailp. 10
  7. The Cybooks Brainp. 11
  8. Monitoring and incidentsp. 12
  9. ISO/IEC 27001p. 13
  10. What we don’t offer yetp. 14
Download the security paper

PDF · 14 pages · 417 KB · Last reviewed 15 Oct 2026

Questions

What IT reviewers ask us first.

Where is my data?

Your books and documents are stored on Amazon Web Services in Frankfurt, in the EU.

Is my data mixed with other companies’ data?

No. Every company gets its own database, its own folder for documents and its own search index.

What if something goes wrong?

We can bring your books back within the available backup history, up to 35 days, and earlier versions of your documents are kept for 90 days.

Can the Cybooks Brain pay someone?

No. It can’t make payments, and your bank connection is read-only.

Does Cybooks see my bank password?

No. You give consent at your bank, through a regulated open-banking provider.

Can I make two-factor sign-in compulsory?

Yes. An admin can require it for everyone in the company, from today or within a week.

Can I see who changed something?

Yes. Every change is in the audit trail with who, what and when. Each record’s history is on every plan; the company-wide log is on Premium.

Do you hold ISO/IEC 27001?

Not yet. We’re putting ourselves through it: internal audit in January 2027, certification audit in February and March 2027.

Do you have a SOC 2 report?

No. SOC 2 is a US framework; we’re working towards ISO/IEC 27001, the international one.

Can I take my data with me?

Yes. Export your reports, including the general ledger, whenever you want, and download any document.

Bookkeeping should happen as your business happens.

On the infrastructure your books deserve: their own database in Frankfurt, fingerprinted and watched. 14 days free, no card.