AutessaDB

Files, apps and operations

AutessaDB is also the backbone for files and apps: Drives, app sign-in tables and per-visitor rules, with soft delete as the safety net.

Create a free database

Drive · Legal/Shared/Legal/ContractsSAMPLE

nametypeversiontext

2026/FOLDER

acme-msa.pdfFILE2EXTRACTED

globex-msa.pdfFILE1EXTRACTED

autessa drive grepSAMPLE

/Shared/Legal/Contracts/acme-msa.pdf:4:12: 12.2 Termination for Convenience…
/Shared/Legal/Contracts/globex-msa.pdf:7:3: 9.1 Termination for Convenience…

-- why it matters

What does files, apps and operations cover?

AutessaDB powers Autessa Drive and custom apps, with sign-in user tables, per-visitor row rules, soft delete and a 14-day restore window.

AutessaDB also carries Autessa's files and apps. Drives are tables of files, custom apps keep their data and their sign-in users here, and soft delete means one wrong click never ends a dataset.

Who works here

Drive members organize files; app builders connect apps to tables and scope visitors with roles; table admins delete and restore.

In one sentence each

Drive on AutessaDB · A Drive is an AutessaDB table of files and folders, so files get the same access rules, agent tools, CLI and SDK as every other table.
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.
Soft delete and restore · Table deletion needs a confirmation token, lands in a trash with 14 days to restore, and ownership can move to a teammate.

-- subtopics

Everything in files, apps and operations

Drive on AutessaDB

A Drive is an AutessaDB table of files and folders, so files get the same access rules, agent tools, CLI and SDK as every other table.

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.

Soft delete and restore

Table deletion needs a confirmation token, lands in a trash with 14 days to restore, and ownership can move to a teammate.

-- on screen

What it looks like

Backend for custom apps

Client Portal · My orderssigned in: kim@harbor.exampleSAMPLE

orderstatustotal

5531shipped1,240.00

5540open86.00

Only Harbor Freight’s rows. The app asks for orders; the database applies the visitor’s rule.

Role · Portal customers → ordersSAMPLE

assigned to: CUSTOM_APP  Client Portal
row rule:    account_id EQUALS $CURRENT_CUSTOMAPP_USER.account_id
writeCheck:  SAME_AS_READ

Soft delete and restore

tables list-deleted14-day grace periodSAMPLE

tabledeletedtime left

old_leadsOct 298 daysrestore

scratch_importOct 221 dayrestore

Deletion is two-step: a short-lived confirmation token, then a confirm that re-checks ADMIN.

-- faq

Questions about files, apps and operations

Is Autessa Drive part of AutessaDB?

Yes. A Drive is an AutessaDB table of files and folders, which is why it shares AutessaDB's agent tools, CLI and SDK.

Can a customer portal show each customer only their own data?

Yes. Give the app an AutessaDB role whose row rule uses $CURRENT_CUSTOMAPP_USER_ID or a column of the visitor's row, and each visitor sees only matching rows.

Can I recover a deleted AutessaDB table?

Yes, within 14 days. Deletion is a soft delete; restore brings the table back before it is purged.

Other areas of AutessaDB

data_modelingTables and data modeling →AutessaDB tables are typed, related and computed: text, number, select and media columns, foreign keys, AutessaScript computed columns, write-once ledger tables and one-click knowledge bases.queries_and_apisQueries, APIs and SDKs →One query model everywhere: the same filters, sorts, aggregates and bulk writes work in the builder, the REST API, the CLI, scripts and agent tools.vector_searchSemantic search and AI →Vector search is a column setting, not a second database: flip it on and AutessaDB indexes, enriches and serves every value to people and agents.row_level_securityRow-level security and access →Every read and write, from a person, agent, script, app or API key, passes through the same row rules, column masks and access log.triggersTriggers and pipelines →Row changes become automation: triggers run tools, agents and writes, chain across tables, and leave a full execution history.data_lakeData lake and analytics →A columnar data lake for events, logs, history and exports: bulk loads, partitions, analytical SQL, a semantic layer, plain-language Ask, data agents and archive tiers, all under the same security as your tables.

$ autessa autessadb tables create

Files, apps and operations, built into one database.

Use it out of the box, then shape it to how your company works. Tables, the data lake, security and triggers are all the same AutessaDB, from the builder, the API or the CLI.

Create a free database

Read the AutessaDB guide or install the CLI.

100% customizable, code and all

Make AutessaDB fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours