Get started

What is the

Modules, components, and delivery model of a platform that runs in your organization's environment.

On this page

The Aptabit Platform is an enterprise platform installed on your organization's own infrastructure. In a single product it brings together document knowledge, structured data, process automation, integrations with your systems, AI models, and governance. It runs on your own Linux servers, including on networks with no internet access.

What the platform brings together

Module What it does
Chat Talks to an enabled model, an agent, or a published flow. Reads attachments, answers from knowledge and data contexts, and generates .xlsx, .pptx, .pdf, .csv, .md, and .txt files.
Agents Combine a base model, instructions, and generation parameters, published only to the workspaces and people you choose.
Storage Knowledge contexts, with documents indexed for hybrid search, and data contexts, with typed tables queried through read-only SQL.
Flows Visual builder with 13 block types and 30 flow templates. A published flow runs in chat, through an HTTP endpoint with its own token, or on a schedule.
Schedules Run published flows at fixed intervals, from 60 seconds.
Integrations Connections to external systems through APIs, with more than 99 ready-made connectors and encrypted credentials.
Settings Users and access, workspaces, models, logs, governance, brand, license, and system.

Where it runs

  • Your own server: Linux on x86_64 or arm64, physical or virtual, as a Docker container stack with Compose v2.
  • Models of your choice: local models on CPU, GPU, or NPU, managed by the platform itself, and external providers (OpenAI, Azure OpenAI, Anthropic, and endpoints compatible with the OpenAI API), side by side.
  • Connected or isolated: with an online license, or on a fully isolated network with a license file.

See Requirements and sizing.

Components

An installation is a stack of ten services:

  • proxy: Nginx, the single HTTP entry point (port 8080 by default).
  • web: the web application.
  • api: the Rust API. Serves chat and runs flows and schedules.
  • worker: background tasks: document ingestion, semantic indexing of messages, and table loads.
  • docker-guard: the only service with access to the server's Docker. It allows nothing but the management of local model containers.
  • postgres: PostgreSQL 16. Stores users, workspaces, flows, runs, data tables, the audit trail, and the task queue.
  • redis: Redis 7, for sessions and for the signal that new tasks are queued.
  • minio: S3-compatible object storage for original files.
  • milvus and etcd: the vector database behind semantic search and its metadata store.

PostgreSQL, Redis, S3 storage, and Milvus can run with the platform or point to services your organization already operates (for Milvus, Zilliz as well).

What stays in your environment

Documents, conversations, prompts, data, embeddings, and files stay in your installation's databases and storage. When you choose an external model provider, requests to that model go to the provider you chose; with local models, they never leave the server.

An installation with an online license sends Aptabit Manager license and installation metadata and, depending on the license's telemetry level, aggregate usage counts. No content is sent. An installation with an offline license never contacts Aptabit. See License and connectivity.

Delivery model

  • Distribution: images from a private registry, with short-lived credentials issued to an active license. On isolated networks, images are carried as a file.
  • Operations: the aptabit CLI checks the machine, installs, updates in stages behind health checks, backs up, and restores, from a single config.yaml.
  • License: online, with periodic check-ins, or offline, with a license file valid for up to 120 days.
  • Predictable cost: you pay only for flows published to production, with no per-user, per-token, storage, or usage charges.

Highlights of version 3.7

  • OIDC SSO with directory group rules, an SSO-only sign-in mode, and a provider connection test.
  • A protected root account: only it changes its own password and e-mail, and it is recovered on the server with a single-use key.
  • aptabit check, which checks the machine before installing.
  • A CLI in Portuguese and English, with failures identified by code and ID, JSON output for status and license, and a support bundle without secrets.
  • First sign-in from the terminal as well, with aptabit setup.
  • A static Linux CLI binary that runs on RHEL 8, Ubuntu 20.04, and Debian 11.

Since version 3.6: licensing by installation key, offline licensing by file, and isolation of the server's Docker through docker-guard.

Next step: review the Requirements and sizing and follow the Quickstart.

Documentationv3.7