What teams build on AutessaDB

Application developers

Need a backend with types, an API and security they do not have to re-write in every client.

uses

• REST API, CLI and SDK · The REST API, the `autessa autessadb` CLI namespace and the `autessa.autessadb` SDK reach the same tables with the same security as the builder.
• Filters, sorting and pagination · Queries take groups of AND/OR conditions with comparison, text, list and null operators, multi-column sorts, and either page numbers or cursors for large tables.
• Row-level security · Row rules decide which rows each caller sees, with placeholders for the current user, teams, roles and app visitors, and edit checks for changes.
• Backend for custom apps · Custom apps read and write AutessaDB tables, keep their sign-in users in AutessaDB, and scope each visitor to their own rows with role placeholders.

AI and agent builders

Need retrieval over documents and records, plus safe write access for agents.

uses

• Semantic (vector) search · Mark a column for semantic search and every write is indexed in the background, enriched by AI, and searchable by meaning next to ordinary filters.
• Knowledge bases · Drag files or whole folders into a knowledge base and they are indexed for semantic search, with a Create Agent shortcut for a ready-made search agent.
• Database tools for AI agents · Ready-made tools give agents insert, update, delete, query, aggregate, semantic query, general search, Drive and data lake access to your tables.
• File and audio search · File columns get an auto-written notes companion and audio columns get a transcript, so documents and calls are searchable like text.

Data and analytics teams

Need a data lake with SQL over billions of rows, and consistent answers when people and agents ask questions.

uses

• Columnar data lake tables · Lakehouse-style columnar tables for events, logs, history and exports, built for aggregations, group-bys, window functions and joins over billions of rows.
• Bulk loading and partitioning · Load CSV and Parquet files or whole AutessaDB tables, append or replace, see every bad row reported, and partition by date so queries read only what they need.
• SQL Workbench · A SQL editor that knows your tables and measures, estimates scan size as you type, keeps history, and downloads results as CSV or Parquet.
• Semantic layer · Descriptions, grain, synonyms, measures, joins and verified queries teach people and agents how to query a table, and Suggest with AI drafts them for review.
• Ask in plain language · Type a question such as "monthly revenue by region this year" and Ask proposes SQL from your descriptions, measures and verified queries. Nothing runs until you click Run.
• Data agents · One click creates describe, query and result tools for the tables you pick, so an agent can answer data questions with SQL, preferring your verified queries.

Security and compliance

Need to prove who saw what, keep sensitive fields masked, and keep records unchanged.

uses

• Column masking and hidden columns · Per role, a column is visible, masked (fully redacted, last four, or a consistent code) or hidden, and masked columns are stored encrypted.
• Data access log · Every read, change and reveal of protected data is logged by table and row, with a chain integrity check and filters by date and action.
• Append-only tables · Append-only tables are write-once: rows can be added and read but never changed or removed, and the setting can be turned on but never off.
• Security roles · A role bundles table policies (row rule, edit check, column rules) and is assigned to people, teams, company roles, everyone, custom apps or API keys.

Operations and automation

Need records that start work when they change, and pipelines they can see.

uses

• Database triggers · A trigger fires on insert, update or delete, checks column conditions, and runs a tool, an agent, a multi-agent or a table update with the row values.
• Pipelines and impact analysis · Triggers that write rows into other tables chain into pipelines, and an impact analyzer maps the cascade and warns about cycles before anything runs.
• Trigger execution history · Every firing keeps a snapshot of the trigger, the row before and after, and the action response, so debugging starts from facts.
• Bulk and batch writes · Bulk calls write many rows by id and batch calls change every row matching a filter, with control over atomicity, triggers, indexing and computed columns.

Business builders (no code)

Need a table they can design in plain language and edit like a spreadsheet.

uses

• DB Copilot · Describe the data you need and the DB Copilot proposes tables and schema changes as cards you apply or reject, and answers questions about your data.
• Tables and column types · AutessaDB tables have typed columns from Short Text to Audio, with required flags, value limits, select lists and system columns on every row.
• Foreign keys and joins · Integer columns can be foreign keys to rows in another table, and join queries follow them with filters, while each joined table keeps its own security.
• Sharing and access levels · Tables start private and are shared at READ, WRITE, PUBLISH or ADMIN, with a default security role applied to everyone you share with.

Healthcare and clinics

Patient-facing portals where each person signs in and sees only their own records, with sensitive identifiers masked for front-desk roles and every reveal logged.

Financial services

Append-only ledgers, masked account and tax numbers, and a data lake of transaction history, queried with SQL and kept on an archive tier for long retention.

Government and public sector

Records requests and case files where row rules keep departments to their own cases, and the access log answers who looked at a record and when.

Legal and professional services

Contracts in a Drive searched by meaning and by exact clause, with matters scoped by team and a client portal per customer.

Customer support and success

Tickets and call notes searchable by meaning, agents that count and summarize, and triggers that route work when a status changes.

Software and SaaS

A backend for internal tools and customer portals, with the REST API, CLI and SDK for CI, migrations and coding agents.