Showcase · live in production
A dealer enters a VIN, uploads photos and answers five questions. Offlot returns finished campaign copy for six channels, a calendar and the leads that come back. The AI assistant in the app creates a vehicle and its campaign after a clarifying question, and you confirm before anything is saved. Live at offlot.app, built end-to-end on Kumiko.

Enter the VIN, Offlot recognises the car, and the campaign copy for every channel is ready.

The Today screen shows what needs a decision, from vehicles to campaigns.

The assistant sets up a vehicle and its campaign, and you confirm first.

A VIN becomes decoded vehicle facts that the dealer checks.
A chatbot can return text. Offlot carries the result through a business process:
VIN or VIN photo, on to vehicle data, photos and dealer details, channel copy, campaign calendar, public vehicle page, enquiry and lead.
The starter catalog configures classifieds marketplaces, WhatsApp, Facebook, Instagram, email and the public landing page for each of the GB and ES markets. Posts are prepared per channel, and for WhatsApp as text to copy. The dealer publishes; Offlot writes and reminds.
Offlot contains the automotive logic: vehicle intake, VIN decoding, campaigns, channel rules, photos, plate review, public vehicle pages and leads. Kumiko supplies what every serious multi-tenant application needs around it: identity, tenant boundaries, files, jobs, secrets, notifications, data rights, tiers and operational screens.
The framework does not replace product thinking, but it keeps product teams from rebuilding the platform underneath every product.
How it is built
VIN photo + vehicle intake
The VIN-photo step returns a validated VIN, which feeds the vehicle intake flow. VIN facts are combined with dealer details, photos and publish checks.
AI document workflows →Plate detection + image review
Number-plate detection returns regions for review. A manual review step sits between detection and any public use of the image.
AI pipeline →Channel copy + prompt store
Channel copy is generated from structured vehicle facts and channel rules. Prompts come from a tenant-scoped, versioned prompt store and can be tried in the AI dry-run screen.
Prompt store →In-app AI assistant
The assistant (Enterprise) asks a clarifying question, proposes the action and a person confirms it before anything is saved.
AI assistant →Provider adapters
The app mounts an Anthropic adapter and an OpenAI-compatible adapter. Provider and model policy live in the AI foundation and pipeline layers, not in domain handlers.
Provider adapters →Kumiko bundled-features
Auth, sessions, user and tenant identity, file storage, jobs, secrets, notifications, data rights, retention, tiers, caps and billing come from the platform, next to Offlot's own features.
Plans and checkout →Where the effort goes
The app owns the domain: vehicles, campaigns, channel rules, plate review, public vehicle pages, leads and the dealer screens. Identity, tenancy, files, jobs, notifications, tiers and billing come from the platform. The Offlot app holds more than 20 app-owned feature modules and more than 400 test files, including more than 140 integration tests (measured and rounded down).
Continue in the docs
The docs take you from the first command to a running app. The Show Pony tutorial walks through the whole path on a real application.