SysForge is built from 55 parts, 13 pieces of glue and 25 apps: 93 services exposing 3,949 operations, counted from the platform's own spec.
How to read this
Every service on the platform describes itself, and this page is built from those descriptions and the platform's spec, not from a diagram somebody drew once. Three kinds of thing are here:
A part. a part does one thing, and any other part can call it: the AI, the files, the geocoder, the text messages.
Glue. glue chains parts together and keeps the result running: the forge that runs a chain, the cron that wakes it, the auth that signs every call.
An app. an app is already assembled from parts, with a face of its own: the field platform, the hospitality dashboard, the radio buyer.
A new job is a chain: parts called in order by a graph, dry-run first, then run live as the person who asked. The recipes below show seven such chains, one of which ran. Every part's page lists its operations and which other parts lean on it.
The rings
Seen from the middle: the core that everything stands on, the parts any chain can call, what is composed from them, and the surface where the platform touches the world: a face for a person, or a door to another system. The dashed chips at the surface are doors that are not services in the spec.
0. Coreidentity, state, storage, time, and the machines themselves: 16 services, 626 operations
Three pieces turn parts into an app, in this order. A job starts as a graph of calls; the forge runs it; stitch keeps the result alive; GroundGame packs the whole thing up.
Forgea graph of calls to parts becomes a service, run as the person who asked
→
Stitchkeeps a running service converging on the state it declared
→
GroundGamepacks the data, the services, the theme and the schedule as one app
Around that spine, the rest of the glue:
AuthWho is asking: sign-in, API keys, permissions and groups for every part on the platform.
CronScheduled jobs: a cron expression, a time zone, and an HTTP call to any part when it fires.
GreenroomPre-flight staging: where a change waits and is checked before it goes live.
HiveThe autonomous-agent control plane: watches the platform, ranks what needs attention, and pauses at an operator's gate before touching production.
InboxA persistent inbox with read state and web-push fan-out for messages between parts and people.
KernelAgent state and graph lint: the rules an agent's graph must pass before it runs.
NotifyThe notification spine: producers post, subscribers get it by text, email or push.
TenantMany tenant instances of the platform, each a complete deployment, managed from one place.
WebhookWebhooks from outside (forms, GitHub, payments) received in one place and routed to the right part.
WorkspacesWorkspaces for several tenants: who is in one and what it holds.
The apps
Already assembled, each with a face of its own. Where an app's own description names the parts under it, they are listed.
PulseBusiness intelligence for hospitality, media and tourism businesses across the US Virgin Islands.
Field appThe field-operations platform: contacts, turf, canvassing, events and the people doing the work.
RadioRural AM and FM rate cards and media buying, with the resources declared rather than hand-written.
AdvertisingThe system of record for advertising operations: advertisers, campaigns, vendors, orders, placements, creatives and spend.Built on: Intel, Radio
ConvoGoal-directed conversations by text message, run by the AI part with a person in the loop.Built on: Executive assistant, SMS
CastDrives physical signage panels and server-side video streams from one routing core.Built on: Weave
ElectionsElection-night engine: live results, broadcast boards and a registry of any race.Built on: Loom
SearchAn answer engine: catalog-gated agents over the AI and Models parts.Built on: AI, Models
BankingCollects the daily files a partner bank drops by SFTP, archives them and parses balances and transactions.Built on: Auth, Cron, Models
BillingUsage and entitlement billing: per-tenant invoices assembled from what the parts recorded.Built on: AI, Auth, Database, Square, Tenant
OnboardOnboarding by a rotating QR code: a progressive trust flow from a scan to an account.Built on: Auth
PersonnelPayroll tracking and per-entity cost allocation for an employer of record.
IssuesIssue tracking over GitHub for every project on the platform.Built on: Infrastructure
Captive portalA guest-capture portal for hospitality properties: the public page collects a visitor, the back end keeps the record.Built on: Database, UniFi
NominateThe consumer face over a comprehensive, current dataset of public elections in the US: every office, race and boundary.
MobileThe back end of the mobile app: canvassing on a phone, offline, synced when back in range.
Forge appThe Forge's own front: announced doors only, with the app's own sign-in on every path.
Save VIAn assembled app: announced doors only, with its own sign-in on every path.
CampaignThe consolidated outreach platform (CRM, field operations, messaging) that succeeds the field app.Built on: Field app
LoomThe workspace builder: composable data dashboards and the narrative around them.
NightAn assembled app: announced doors only, with its own sign-in on every path.
Victory ModelingAn assembled app: announced doors only, with its own sign-in on every path.
HQAn assembled app: announced doors only, with its own sign-in on every path.
Recipes: parts chained into something useful
A recipe is written in a few words the forge understands. Each step is one call to a part, or a turn of the graph:
Word
What it does
mesh.call
call any part by the operation's name in its spec, as the person who asked
ai.chat
ask the AI part a question, with the data so far in the prompt
json.parse
turn an answer's text into data, leniently
foreach
do a step once per row
branch
take one path or another
wait
sleep until a job finishes or a person releases a gate
ensure
refuse to go on when an input is wrong
emit / let
name a value for later steps
digest / now
hash a document; stamp the time
db.query / fql.query
read a catalog, or several at once
Seven chains. The first ran, and its numbers are what it found; the other six are the platform's own worked scenarios, each a real request resolved by a handful of parts.
Companies near home: find them, watch them, read their jobs and newsran
“Every company within a few miles of home: what they do, what they are hiring for, what the news says.”
Result: A heat map of attendance and a ranked follow-up list. From the platform's composability scenarios, March 2026.
Most leaned on
Which parts the others name in their own descriptions. 96 such mentions across the 93 services; the hubs are what every chain ends up calling.
Named by other partsmentions
Parts named by the most other parts
AI10
Auth10
Cron9
Models8
Intel7
Database4
Loom4
Overseer4
SMS4
Files3
Infrastructure3
Scout3
The MCP catalogsysforge.aiThe platform's own name for the fleet, and every service id, is on each part's page.
forge-catalog.json, generated Oct 30, 2026
Services, operations and the mention graph from the platform's unified OpenAPI spec, refreshed nightly. Names, tiers and recipes from a hand file in this site's repo.