The short version

These are not competitors, and pretending otherwise would be dishonest. 8090 sells a way for regulated enterprises to get applications built, connecting business intent, requirements, architecture, work orders, code, testing and production maintenance into one governed pipeline that people and agents share. It raised a $135M Series A led by Salesforce in June 2026 and works with healthcare, insurance, life sciences, aerospace, energy, manufacturing, financial services and US government customers.

Last Light does something much narrower: it sits on repositories you already have and keeps them healthy. Issues get triaged, pull requests get reviewed, security sweeps run weekly, fixes get proposed. It does not take requirements, it does not produce an application, and it does not come with a delivery team.

The term "software factory" covers both because both describe software work as a production line. But one is a line for building new systems under enterprise governance, and the other is a line for maintaining existing repositories.

Side by side

Last Light8090
What it produces Maintenance of existing repos: triage, review, fixes, reports New or modernised enterprise applications
Starting point A GitHub repository and a webhook Business intent, requirements, architecture
Buyer A platform or engineering team An enterprise programme, often with a systems integrator
Delivery Software you install and run A platform, or a full build-host-manage engagement
Hosting Self-hosted only, by you Vendor-hosted or vendor-managed
Governance Approval gates, scoped tokens, and a full transcript of every run, all on your infra Governance and audit of every decision, by design
Industries Any team on GitHub Regulated: healthcare, finance, aerospace, government
Licence MIT, free, source on GitHub Commercial, enterprise contract
Time to value An afternoon, if you can run Docker A procurement cycle and a delivery programme

Where each one wins

What 8090 does that Last Light doesn't

  • Takes business intent as input. Requirements, architecture and work orders are first-class artefacts; Last Light starts at a GitHub issue.
  • Builds and modernises whole applications, including legacy replatforming. That is far beyond repo maintenance.
  • Traceability from business intent onwards. Requirement to work order to deployment is one governed chain. Last Light's trail is thorough but starts at the GitHub event, so it cannot tell you which requirement a change served.
  • A managed option where 8090 builds, hosts and runs the application for you.
  • Enterprise motion: contracts, accountability, and partnerships such as the EY.ai PDLC launch.
  • Capital and scale behind the roadmap.

What Last Light does that 8090 doesn't

  • Runs entirely on your own infrastructure, with your model keys. Nothing is vendor-hosted or vendor-managed.
  • Is free and MIT-licensed, with the whole implementation readable on GitHub.
  • Installs in an afternoon: a GitHub App and a Docker stack, not a procurement cycle.
  • Is event-driven on the repo itself. Webhooks, Slack and cron, reacting continuously rather than running a delivery programme.
  • Is forkable end to end. Every workflow, prompt and persona is config you can override.
  • Keeps the whole record itself. Every phase, tool call, approval and dollar of cost is persisted to SQLite plus a per-session JSONL transcript on your own disk, browsable in the dashboard and exportable as OpenTelemetry traces. None of the audit trail depends on a vendor keeping it for you.
  • Fits a single team without an enterprise programme around it.

Which should you pick?

Choose 8090 when

you need applications built or modernised in a regulated environment, the audit trail from business intent to production is a compliance requirement, and you're buying a platform and a delivery capability rather than installing a tool.

Choose Last Light when

the code already exists and the problem is keeping up with it (triage, review, security sweeps and small fixes) and you want that running on your own infrastructure, for free, with every behaviour open to inspection.

These can also coexist: nothing about an enterprise build programme prevents a self-hosted maintenance agent running on the repositories it produces. Details about 8090 are point-in-time (June 2026) and drawn from public sources. See the sources on the comparisons hub.

Compare against something else