Core Concepts
Five concepts cover nearly everything you do on the platform.
Project
The project is the boundary. It holds your automations, your tables, your portals and your environment variables, and it is inside it that one thing reaches another — a portal only runs automations from its own project, an automation only reads its account's tables.
Automation
An automation runs a single, independent process.
- Each one is a Python function decorated with
@automation. - The decorator marks the entry point of your script.
- It receives data through a
seedargument, a serializable JSON object.
Deployment
datallog login and datallog push take your code to the cloud. The push builds the image, publishes the automations and applies the table declaration — everything the platform needs to know comes out of your own code.
Tables
Your automation keeps data with no database to administer: you declare the table in code, the push creates what is missing, and the declared table knows how to write and read.
leads = table("leads", fields={"company": Text(), "stage": Text(index=True)})
leads.insert({"company": "Acme", "stage": "open"})Portals
A portal is a page of yours, hosted by the platform, with its own address, where people who do not use the dashboard see what an automation produced — and run it with one click.
How the automation responds
In the background, the call confirms the request and the result arrives later through the webhook and the history. Waiting for the result, it comes back in the response itself — that is what lets a portal answer in seconds.