Skip to content
Abada Platform

Quickstart

The installer requests a Gemini API key with hidden input, validates access to gemini-3.6-flash, retrieves the checksummed release archive, and starts the local HTTP platform.

Terminal window
mkdir abada-quickstart && cd abada-quickstart
curl -fsSL https://install.abadaplatform.com/install.sh | bash

Automation may supply ABADA_AGENT_LLM_API_KEY to the bash process. The key is stored only in the untracked local .env.dev with mode 0600; it is never part of the release archive or Studio runtime configuration.

One command brings up the whole platform: PostgreSQL, the Engine, the Studio operator UI and the Agent Worker (abada-agent-worker), behind a local HTTP edge with bundled Keycloak identity. The installer also enables the Insight Engine so the governed optimization loop can observe the runs you create.

The current launcher finishes with a success panel that confirms container health and groups URLs, starter accounts, first-run guidance and management commands. It includes:

  • Studio: http://studio.localhost (dev) / http://localhost:5605
  • Engine information: http://api.localhost/api/v1/info
  • Keycloak: http://keycloak.localhost (development identity only)
  • Agent Worker health: GET /api/v1/projects/{projectId}/workers/health (shown in Studio Operations)

Use alice / alice to sign in to Studio. Studio is the single operator UI: its Header tabs cover Designer, Task Inbox, Operations and Insight, and the Administration button is gated on the abada-admin JWT group. These credentials are local development data and must never be reused in production. On the first login, Studio creates and deploys the AI Lead Triage starter and opens its auto-layouted diagram. The Deploy & Start dialog contains HIGH, MEDIUM and LOW inputs plus an explicit action for four LOW Insight samples. The Gemini calls run sequentially with a quota-safe delay, so allow about five minutes. Alice initializes and operates the project. A HIGH result creates a human task exclusively for bob / bob; Bob opens the same Starter project in Studio, claims the review, completes its form, and returns execution to the local demo adapter. The Insight proposal call uses a bounded 90-second Gemini timeout.

The original immutable 1.0.0-rc.1 archive prints the same URLs in a compact summary. The structured success panel is included in subsequent release bundles and when running the current repository launcher.

Windows PowerShell:

Terminal window
New-Item -ItemType Directory abada-quickstart
Set-Location abada-quickstart
Invoke-WebRequest https://raw.githubusercontent.com/bashizip/abada-platform/main/release/quickstart.ps1 -OutFile quickstart.ps1
.\quickstart.ps1 -Version 1.0.0-rc.7

Abada’s release-image contract supports linux/amd64 and linux/arm64. The original 1.0.0-rc.1 images contain only linux/amd64; on an ARM64 host, the launcher prints a notice and uses Docker’s compatibility mode for that immutable release. Subsequent release manifests are validated for both native platforms.

Verify and tear down:

Terminal window
curl -fsS http://api.localhost/api/actuator/health/readiness
cd abada-platform
./release/abada-platform status dev
./release/abada-platform down dev