launch.ist
Sign in Start free
The team

Some team members are software. All of them are audited.

Four specialist agents. Human engineers who review everything they produce. Credentials scoped to one task, revoked when the session ends. Nothing ships without a human name on the merge.

Developer agent

Refuses to ship code it can’t cite.

developer-agent
Included with every plan

The one that signs commits.

Every change it opens carries a full provenance record: sources cited, versions pinned, CVEs checked against the GH advisory DB, licenses cleared against your project SPDX, and tests passing before the PR opens. On frontend work it goes further than the test suite — it opens the running app in a real browser and clicks through the actual flows, the way a user would, catching what a unit test can’t see. If it can’t verify a claim, it surfaces the gap instead of papering over it.

  • Plans visibly before touching the repo.
  • Pins every dependency it pulls in.
  • Cites the doc for every API call.
  • Runs the test suite before opening the PR.
  • Drives the running frontend in a real browser — clicks through the actual flows, not just unit tests.
  • Checks CVEs against the GH advisory DB.
  • Verifies license compatibility against your project SPDX.
  • Annotates every claim in the diff with its source.
  • Refuses unverifiable changes — surfaces, doesn’t silently fake.
    • mcp Cursor · Claude Code · VS Code
    • git GitHub · Gitea · GitLab
    • ci GH Actions · CircleCI · Buildkite
    • langs ts/js · python · go · rust
    Open developer agent Install MCP server →
    developer agent tally-fm/api 11:42 UTC
    Add Stripe webhook handler for invoice.paid events.
    1. Pinned stripe@15.6.0 npm · today
    2. Webhook signature verified per docs stripe.com/docs · 2024-09
    3. Idempotency key checked stripe.com · best-practices
    4. Replay attack regression test vitest 1.6.0
    5. License clearance (MIT) SPDX
    Provenance saved · view trail →

    Designer agent

    Catches off-system colors, radii, and spacing before they ship.

    designer-agent
    Included with every plan

    The one that protects the system.

    Generates components and screens against your existing token set. Before any new element ships, it scans what’s already in the system. If a component fits, it reuses it. If something is new, it writes the token diff alongside the screen and hands off a PR-ready package — code, Figma library, and tokens in step.

    • Reads your existing tokens and components.
    • Catches off-system colors, radii, spacing.
    • Writes the token diff alongside the screen.
    • Outputs Figma libraries and code in step.
    • Annotates contrast and hit-target failures.
    • Generates dark mode tokens that pass WCAG AA.
    • Refuses to add a new component if one fits.
    • Hands off a PR-ready package — code + Figma + tokens.
      • mcp Figma · Cursor · Claude Code
      • output React · Vue · Svelte · CSS
      • tokens Style Dictionary · Tokens Studio
      • a11y WCAG 2.2 · contrast · hit-target
      Open designer agent Install Figma plugin →
      designer agent turnstile/web 14:08 UTC
      Add a callout component to the system.
      1. No off-system colors tokens.json · 47 refs
      2. Radius matches card (6px) --radius-md
      3. Contrast 7.1:1 — passes AA + AAA WCAG 2.2
      4. Figma library updated v0.4.2 · published
      5. No similar component existed components/* · scanned
      Provenance saved · view trail →

      Lawyer agent

      Every dependency has a license. Every license has a clause. This one reads them.

      lawyer-agent
      Included with every plan

      The one that reads the fine print.

      Works alongside the developer agent at the point where code is written, not after it ships. Checks license compatibility across your full dependency tree, flags copyleft contamination before it lands, and maps your regulatory surface — GDPR, HIPAA, PCI DSS — against your actual data flows. Anything ambiguous goes to a human. It never guesses.

      • SPDX license compatibility across your full dep tree.
      • Detects ToS changes in APIs you depend on.
      • Maps regulatory surface — GDPR, HIPAA, PCI DSS.
      • Flags copyleft contamination before it lands.
      • Generates compliance checklists per jurisdiction.
      • Reviews data-flow for cross-border transfer risks.
      • Annotates every finding with the source clause.
      • Hands off to a human for anything ambiguous.
        • mcp Cursor · Claude Code · VS Code
        • sources SPDX · OSI · EU AI Act · GDPR text
        • output compliance reports · license audits
        • works with developer agent · designer agent
        Open lawyer agent Install MCP server →
          Provenance saved · view trail →

          DevOps agent

          Isolated Kubernetes, GitOps, observability. Just bring your domain name.

          devops-agent
          Alpha — available on request

          The one that sets up production.

          Provisions your environment and keeps it running. Isolated namespaces or dedicated clusters. GitOps pipelines that deploy on push. Postgres with backups, Valkey, MinIO, NATS, Grafana — from the platform catalogue, not improvised. Currently in alpha; we are honest about that.

          • Provisions isolated k8s namespaces or dedicated clusters.
          • Configures GitOps pipelines — push to deploy.
          • Deploys catalogue services: Postgres, Valkey, MinIO, NATS, FerretDB.
          • Sets up Grafana observability — logs, metrics, alerts.
          • Manages TLS certificates and ingress automatically.
          • Configures backups and disaster recovery.
          • Monitors logs and surfaces anomalies.
          • Currently in alpha — available on request.
            • mcp Cursor · Claude Code · VS Code
            • platform Kubernetes · Flux · Cilium
            • catalogue Postgres · Valkey · MinIO · NATS · more
            • observability Grafana · Loki · Prometheus
            Request alpha access Learn more →
              Provenance saved · view trail →

              How every agent gets access — and loses it.

              Three steps. The same sequence for all agents. The verifier set differs by role; the human signature at the end does not.

              1. 01 [plan]

                It writes a plan first.

                Files it will touch. Sources it intends to cite. Verifiers it will run. You can revise or veto before it starts.

                task
                scoped per change
                touches
                files + token diff
                sources
                docs + system tokens
                verifiers
                agent-specific set
              2. 02 [run]

                It runs the verifiers as it goes.

                The agent runs its verifiers as it works. Every claim is checked against its source. A failed check stops the run and records the failure in the trail — the run does not continue, and the failure does not disappear.

                pinned
                deps + tokens
                cve
                gh advisory db
                contrast
                WCAG 2.2 AA
                tests
                your suite
              3. 03 [ship]

                A human signs it.

                A human engineer reviews the trail, the verification results, and the output. The trail path (/launches//) is written at review time. Nothing ships without a human taking responsibility. The trail outlives the run — re-runnable months later to detect drift.

                trail
                /launches/<date>/<sha>
                signer
                engineer · reviewed + signed
                recheck
                on dependency update
                archive
                outlives the run
              Start free

              Point it at a repo and see what it surfaces.

              50 verified runs on the free plan. No card required. Upgrade for unlimited runs and private repos — see pricing for current tiers. Human engineers review and sign everything.

              Start free See pricing How verification works →