Document OCR

Straventa Document OCR turns Indonesian paperwork into typed fields. Eleven document types ship with field schemas out of the box, extraction runs synchronously or as a job with webhooks, and every document type carries a retention class the tenant cannot weaken — non-KYC output expires on a 7-day clock while compliance-bound output stays on the statutory one. Run it in our cloud or inside your own infrastructure.

Book a Demo

At a glance

Structured extraction for Indonesian documents — KTP, Kartu Keluarga, NPWP, NIB, Faktur Pajak, and bank statements — as an API you can self-host.

Runs in the Straventa cloud or inside your own Kubernetes or Docker. Retention classes are enforced by a platform-owned document-type registry, not by tenant configuration.

What it does

Built for the work, end to end

Seven Indonesian document types

KTP, Kartu Keluarga, NPWP personal and badan, NIB, Faktur Pajak, and Rekening Koran — with per-bank statement variants for BCA, BNI, BRI, and Mandiri.

Typed fields, not raw text

Each document type declares its own field schema — a KTP returns NIK, nama, tempat and tanggal lahir, alamat, and the rest as named fields, not a blob of text you have to parse.

Sync or async extraction

Post a document and get fields back on the same request, or create a job and receive a webhook when the result is ready.

Per-tenant schema overrides

The platform ships a seed schema per document type; a tenant can PUT its own version and that version survives redeploys.

Scoped API keys

Issue, list, and rotate OCR API keys with their own scope, separate from the rest of the platform's credentials.

Retention a tenant cannot weaken

The document-type registry is platform-owned: non-KYC extraction expires on a 7-day transient clock, while compliance-bound output such as KTP stays on the statutory retention class. A tenant cannot move its KTP schema onto the short clock.

How it works

From kick-off to day-to-day

Pick the document type

Choose from the seven seeded Indonesian types, or PUT your own field schema for a document we do not ship yet.

Send the document

POST it for a synchronous result, or create a job and let the webhook tell you when extraction finished.

Read typed fields

Take named fields straight into onboarding, ledger, or reconciliation — and let the retention clock expire the source on its own.

How it compares

Four ways to read an Indonesian document

The global OCR platforms are excellent general engines that know nothing about a KTP. The local KYC vendors know the document but sell you a whole onboarding flow. Written for whoever has to justify the choice.

Four ways to read an Indonesian document
Criterion	Straventa Document OCR	Google Document AI	AWS Textract	In-house Tesseract
Indonesian document types	Eleven seeded types — KTP, Kartu Keluarga, NPWP personal and badan, NIB, Akta, SK Kemenkumham, SIUP/TDP, Faktur Pajak, Rekening Koran, and a freeform type for anything without a schema.	General forms, invoices, and a set of identity parsers that do not cover Indonesian national documents.	General forms, tables, invoices, and IDs; no Indonesian national document types.	None. You author every field rule yourself.
What comes back	Named fields declared by the document type's schema — a KTP returns nik, nama, tempat_lahir, alamat and the rest, ready to use.	Entities and key-value pairs you map onto your own field names.	Blocks, key-value pairs, and tables you map yourself.	Raw text and coordinates. The parsing is your project.
Deployment	Straventa cloud, or self-hosted inside your own Kubernetes or Docker — same product.	Google Cloud only.	AWS only.	Anywhere — you operate it.
Where the document goes	On a self-hosted deployment, nothing leaves your environment.	Google Cloud regions.	AWS regions.	Your environment.
Retention of extracted data	Set by a platform-owned document-type registry: non-KYC output expires on a 7-day transient clock, compliance-bound output such as KTP stays on the statutory class. A tenant cannot move a KTP schema onto the short clock.	Your own lifecycle configuration; nothing stops a misconfiguration.	Your own lifecycle configuration; nothing stops a misconfiguration.	Whatever you built, if you built it.
Custom document types	PUT your own field schema per tenant; your version survives redeploys and platform seeding.	Custom processors, trained and hosted in the vendor's platform.	Custom queries and adapters within the vendor's platform.	Yours to write, and yours to maintain.
Fits the rest of the stack	Extraction feeds KYC/KYB onboarding and reconciliation on the same platform, under one contract and one login through Straventa Accounts.	An integration project.	An integration project.	An integration project.
Pricing model	Quoted per volume, or per deployment when self-hosted. Contact us.	Per page, per processor, on the vendor's public rate card.	Per page, by API, on the vendor's public rate card.	No licence — you pay in engineering time and accuracy work.

Competitor rows describe each vendor’s publicly documented model at time of writing; confirm current terms with the vendor before making a decision.

How it is priced

Priced on the volume you actually run — or per deployment when it lives in your data centre

Billing model

Per volume, or per deployment

Cloud extraction is quoted against monthly document volume and the document types you use.
Self-hosted is licensed per deployment, so a high-volume year does not become a per-page bill.
Compliance-bound documents carry their statutory retention regardless of tier — that is not a paid add-on.
Billing is not yet active and no payment is collected today; talk to us and we will quote the shape that fits.

See the full price list

Want Document OCR for your team?

Bring your rails, controls, and deployment constraints. We will show where the platform fits and where it does not.

Book a Demo Talk to Sales