At a glance
فاLive demo
Audit Trail View

Your audit trail,
at a glance

AtView collects events from your apps and databases, keeps them append-only, and answers who did what, when and from where — in seconds.

Open the live demoTalk to us

No installation · demo user: demo / demo

Official release · End of Azar 1405 (21 Dec 2026)

—
days
—
hours
—
minutes
—
seconds
Data model inspired byCADFOCSFNIST AU-3PCI DSS 10.2
Why an audit trail?

When something happens, the answers must be ready

For debugging, security reviews or an auditor’s question: know what happened as fast as possible.

5W

Who, what, when, where, result

Every event carries five standard answers — not an unstructured log line you have to guess from.

1×

Written once, never altered

The events table is append-only. Updates and deletes are blocked at the database level.

<1s

Found in seconds

Full-text search and filters over millions of events, with live results and a timeline.

Features

Everything you need to read the trail

Simple to use, precise to review.

One event model

Every source is stored in the same standard shape, so search and reports work the same way.

Persian-aware search

Arabic/Persian letter variants and Persian/Latin digits match each other; the zero-width non-joiner never gets in the way.

Filters and timeline

Click a bar to zoom into a period; narrow results with facets.

History of every entity

See what happened to an invoice or customer, with the value before and after each change.

Tamper-resistant storage

Records are only ever added — even a database admin cannot rewrite history with a simple UPDATE.

Persian-first, Jalali dates

Right-to-left UI, Jalali and Gregorian calendars, the Vazirmatn font and a dark mode.

Mobile & installable

Fast and responsive on phones, and installable as an app (PWA).

One API call to log

Send an event with a single POST; up to a thousand per batch, with duplicate protection.

Automatic database change capture (CDC)Soon

Turn database row changes into events automatically — without touching your application code.

Multi-tenantSoon

For the SaaS edition: every customer’s data fully separated and manageable.

Hash chain for proof of integritySoon

Prove that no record has changed since it was written.

How it works

Three steps to the trail

From logging an event to finding it, with no extra ceremony.

1

Collect

Your apps send events through the API. Database changes will be captured automatically soon.

REST APIBatchCDC · soon
2

Store

Records are validated, normalised and stored append-only; nothing is ever rewritten.

ValidationAppend-onlyIndexed
3

Explore

Search, filter, timeline, entity history and CSV or JSON export.

SearchTimelineExport
Anatomy of an event

Structured for machines, readable for people

One simple event — as it is recorded, and as it appears in the UI.

{
  "category": "data_change",
  "action":   "update",
  "outcome":  "success",
  "initiator": { "name": "ali.rezaei", "roles": ["accountant"] },
  "target":    { "type": "Invoice", "id": "INV-20931" },
  "change": { "fields": [
    { "path": "status", "old": "draft", "new": "approved" }
  ]},
  "source":    { "system": "erp-web", "service": "sales-service" },
  "eventTime": "2026-10-16T17:32:08Z"
}
Who
Ali Rezaei · accountant
What
Updated invoice INV-20931
statusdraft → approved
When
16 Oct 2026 · 17:32:08 UTC
Where
erp-web · sales-service
Result
✓ Success
Supported formats

What you send and what you get back

Input, output and data formats, each with its status today.

Input

  • JSON · HTTP✓ Ready

    Send one event or a batch of up to 1,000 per request; duplicates are ignored.

  • CDCSoon

    Database row changes are turned into events automatically.

Output

  • CSV✓ Ready

    UTF-8 with Excel support and Persian text; the current search results (up to 1,000 rows).

  • JSON✓ Ready

    The current search results, ready for other tools.

  • JSON · event✓ Ready

    Copy one event in full, with every detail, from the details panel.

Data & display

  • Event JSON✓ Ready

    A standard structure: who, what, when, where, result, and the values before and after a change.

  • ISO 8601✓ Ready

    Times are stored in UTC and shown with the Jalali or Gregorian calendar.

  • UTF-8✓ Ready

    Persian, Arabic and English; Persian and Latin digits.

Other formats (such as Syslog or CEF) are not supported yet. Tell us if you need them.

Deployment

Run it wherever you need

Hosted or on your own servers — same interface, same features.

Hosted (SaaS)

No installation or upkeep: create an account and start sending events.

  • Up and running in minutes
  • Updates and backups handled for you
  • Great for a quick start and small teams

On your own servers (on-premise)

Installed on your own infrastructure; data never leaves your network.

  • Simple installation and setup
  • Your own database, under your control
  • For organisations that must keep data in-house

Try it right now

The live demo has sample data: search, filter and open the history of an entity.

Open the live demo
User namedemoPassworddemo
FAQ

Questions we usually get

Ordinary logs are for developers debugging an app and have no fixed shape. AtView answers “who did what”: every event has a standard structure, is stored immutably and can be searched by non-developers through the UI.

Contact

Let’s talk about your needs

Tell us a few lines about your systems and event volume and we will prepare a fitting proposal.

New email
Your details are used only to answer this request.