Build on Aktor

Solutions

Package a business application, with its data, assistant and evals, and deploy it as one unit.

A solution is your own agentic product built on Aktor: a maintenance desk, a helpdesk, a recruiting pipeline. It's a folder of plain files, installed into an organization as one unit:

my-app/
  aktor.yaml                 the manifest: entities, workspaces, assistant, seed, webhooks, evals
  workspaces/*.yaml          pipelines, triggers, safety, budgets
  skills/<name>/SKILL.md     know-how for its agents
  knowledge/*.md             reference text they search
  evals/*.yaml               expected behaviour, checked for real
format: 1
name: property-mgmt
title: Property management
version: 1.2.0
requires_platform: ">=1.2.0"
inputs:
  - { key: company_name, default: Acme Properties }     # workspaces see {{ vars.company_name }}
connectors:
  - { name: sms, plugin: twilio-sms }                    # secrets are asked for at install, never packaged
entities: { … }                                          # the data model
workspaces: [ { file: workspaces/maintenance-desk.yaml } ]
assistant: { … }                                         # what your customers talk to
evals: [ { file: evals/urgent-leak.yaml } ]

The shortest path: on Solutions, open a template (or New solution and describe yours to Design with AI), change it, Deploy, then follow the Integrate tab: create an app key, copy the code for your stack, and tick off the go-live checklist. See Connect your app.

Build it in the dashboard: Solutions → New solution opens the builder. It has forms for the data model, workspaces, triggers, the assistant, connectors, knowledge, skills and evals, checked against the server as you go. Deploy installs it from the page, with no files and no CLI. Package (.zip) downloads the same package for git or the CLI, and Edit YAML lets you change the text and apply it back to the forms. Edit in builder opens an installed solution.

A solution never needs changes to Aktor. It's assembled from the same primitives you'd use by hand, under the same quotas, policies and audit. A package can't grant itself more than an Admin could configure.

Upgrades change only what the new version changed. Workspaces are matched by key. A pipeline gets a new version, and runs in progress finish on the old one. Webhooks keep their URLs. Edits people made in a workspace survive an upgrade that didn't touch them. Every install and upgrade is in the install's history.

Changed a solution's workflow on its canvas? The workspace list marks the workflows a solution made, and their canvas says when the pipeline differs from the version deployed. Save to solution (Admins) writes the pipeline into the solution's aktor.yaml as the next patch version and deploys it, keeping the rest of the file as written, so the builder and later deploys keep your changes. A deploy that would replace changes made in a workspace warns first. Two complete examples are on Solutions → Templates: property management and helpdesk.