Platform Services (BaaS)

kis.ai isn’t only a CLI, it’s a Backend-as-a-Service (BaaS) platform. The backend is a set of independent service binaries (the *.svc files installed by kvm into ~/.kisai/bin/). Each has an internal codename, a focused job, and its own command-line interface for running and bootstrapping it.

You operate them three ways: kvm installs/updates them, kis services start/stop/restart them, and kis info inspects them. Several kis commands are clients of these services, e.g. kis config/kis sd talk to infinity-config, and the gateway provider talks to Loki.

The service map

kvm install all (or kis-platform / baas-full) lays down ~35 service binaries. They’re grouped below by function. Many carry an internal codename. Every service also has a version subcommand (omitted from the tables for brevity).

Edge & gateway

Binary	Codename	Role	Run/CLI
`gateway.svc`		API Gateway, TLS-terminating, multi-tenant edge proxy	`config`
`ai-gateway.svc`	Loki	AI gateway, one endpoint fronting many model providers (the `gateway` provider)
`harbor.svc`	Harbor	Distribution server	`keygen`, `serve`

AI & knowledge

Binary	Codename	Role	Run/CLI
`ai-flow.svc`	arka	AI flow orchestrator	`agent`, `local`
`ai-bot.svc`	Echo	Chatbot substrate: channel adapters, staged NLU cascade, response orchestration, lib-maya bot scripts
`morph.svc`	maya	Maya Execution Service, isolated script execution (the engine behind `script`/`solve`)
`search.svc` / `know.svc`	Sofia	Lexical + semantic search

Data & storage

Binary	Codename	Role	Run/CLI
`data.svc`	seshat	Data services / data-lifecycle layer	`config`, `data`
`datapipe.svc`		Data-pipeline orchestrator	`agent`, `local`
`meta.svc`		Component data serving (embed products into a binary)	`config`, `embed`, `embed-info`, `serve`
`ingest.svc`		Capture traces & logs → logstore	`generate`
`backup.svc`	Thoth	Backup/restore, scheduling, and backup validation
`content.svc`		Content/media service (needs libvips)

Workflow, jobs & rules

Binary	Codename	Role	Run/CLI
`automate.svc`	vulcan	Distributed workflow orchestrator (coordinates vulcan agents)	`agent`, `build`, `cli`, `local`
`workflow.svc`		Workflow orchestrator	`agent`, `local`
`jobs.svc`	ravana	Environments, products, pipelines & job execution	`agent`, `execute`
`rules.svc`	varuna	Business-rules execution engine

Identity, security & secrets

Binary	Codename	Role	Run/CLI
`iam.svc`	janus	Identity & access management (see IAM)	`config`, `data`, `seed`, `tenant`
`vault.svc`		Certificate / secret services (see Vault)	`cert`, `config`, `server`
`vault-agent`	Vault Agent	Per-node Vault daemon	`doctor`, `init`, `install`, `run`, `status`, `uninstall`, `upgrade`
`audit.svc`		Accepts and stores audit records from kis.ai services	`generate`
`argus`	Argus	Runs profile-configured security scanners over source trees	`consolidate`, `enrich`, …

Platform, config & ops

Binary	Codename	Role	Run/CLI
`config.svc`	infinity-config	Hive configuration + service discovery server (the `config`/`sd` backend)	`config`, `explain`, `import-legacy`, `migrate`, `server`
`supervisor.svc`		Keeps a declared set of services in their desired state	`daemon`, `install-daemon`, `install-service`, `restart`, `server`, `start`, …
`forge.svc`	Forge	Environments/products/pipelines management	`generate`
`root.svc`	root	Environments/products/pipelines management	`generate`
`integrate.svc`	r2d2	Integrations management	`generate`
`code.svc`	brahma	App generation from Meta templates (the `code` backend)
`status.svc`		Status APIs	`generate`

Observability & comms

Binary	Codename	Role	Run/CLI
`observe.svc`	querier	Query logs and traces
`telemetry.svc`		Telemetry APIs	`generate`
`notify.svc`		Notifications across email, SMS, push, WhatsApp, in-app, webhook	`generate`
`rtc.svc`	Naarada	Chat / channels / teams

Dev & test

Binary	Role	Run/CLI
`test.svc`	Test execution & automation	`agent`, `api`, `load`, `orchestrator`, `test`, `tests`
`bff.svc`	Backend-for-frontend	`generate`
`scraper.svc`	Scraping service

Also installed: kis.ai, a monolithic all-in-one build with every CLI command in one binary; llama-server, a bundled llama.cpp server for local model serving.

Common patterns across services

Run the service, server (infinity-config), serve (meta), or a mode like agent / local / execute (arka, ravana). Workers typically run in agent mode; orchestrators run in local/execute/server mode.
Scaffold config, generate prints or writes a curated example configuration for config.svc, data.svc, and meta.svc.
Migrate / import, migrate applies a major-version schema migration and import-legacy converts legacy clusterstore/customerstore trees to the new hive layout on infinity-config.
version, every service binary has a version subcommand.

# Examples (each binary lives in ~/.kisai/bin and is run directly)
config.svc server                 # run the infinity-config server
config.svc generate               # print a curated infinity-config example
jobs.svc execute                  # run ravana (jobs) in execute mode
jobs.svc agent                    # run a job worker
data.svc generate                 # print a baas-seshat bootstrap example
meta.svc serve                    # serve local folders / git repos as components
ai-gateway.svc --help             # Loki (AI gateway) options

Installing the BaaS stack

Services come as kvm bundles:

kvm bundles                       # list bundles
kvm install baas-core             # essential BaaS services
kvm install baas-full             # all BaaS services
kvm install ai-full               # all AI services
kvm install kis-platform          # BaaS + AI + dev tools (everything)
kvm install iam.svc               # a single service (here: IAM)

Then manage what’s running with kis services and inspect with kis info. Each service’s own --help documents its config files and run modes.