Skip to content

komp.ac documentation

Understand the data model, server behavior, and calculation rules used by komp.ac.

Server setup and API overview

Documented for server v0.8.40. Environment, database configuration, boot sequence, and the gRPC services behind the API. Read about server setup →

Auth

Accounts, access tokens, the two-plane permission model, grants, role hierarchy, and the audit log. Read about auth →

Accounting-period and global profiles

Separate period-specific books while sharing master data through the reserved global profile. Read about profiles →

Table data

Read and write rows, preserve linked versions, archive history, and control cross-profile updates. Read about table data →

Steel

Understand computed columns, dependencies, client previews, and authoritative server validation. Read about Steel →

Bulk import

Load prepared rows while preserving validation, scripts, accounting effects, and Search indexing. Read about bulk import →

Accounting

See how business rows create journal lines, update accounts, and move through period close and approval. Read about accounting →

Search

Understand searchable values, matching, ordering, permissions, and index consistency. Read about Search →

Search2

Use live single-table filtering, SQL comparisons, ordering, and exact result counts. Read about Search2 →

Analytics

Build permission-aware reports with live profile data, joins, aggregates, and streamed results. Read about Analytics →

Migrations

Understand how the server schema evolves and what the public tables in the server database are. Read about migrations →

Client setup and first launch

Documented for client v0.8.31. Build and run the terminal client, connect it to a server, and sign in. Read about client setup →

Authentication and accounts

Sign in, register, change or reset passwords, and understand the stored session and roles. Read about authentication →

Web UI setup and overview

Documented for web v0.8.38. Run the browser frontend, reach the admin panel and analytics, and understand its architecture. Read about the web UI →