Loams v0.1.0 is out: run the whole stack yourself with Docker Compose. See the roadmap

11 stars on GitHubLoams on DiscordConsole
Loams Cloud marketplace · Listing #1

From error to fix to deploy, in one loop you can stop.

Loams Desktop already embeds the collaboration and observability apps, with agent tooling, MCP, an agent bus, browser providers and console plugins. Software Factory connects these into one Loams Bot workflow, from evidence to an approved change.

Request early accessExplore the open design and source
Early accessOpen sourceHosted or self-hosted

Early access. Plugin lifecycle, agent tooling, app adapters, browser providers and console foundations are implemented. This page illustrates the complete workflow being integrated; a site account does not provision a hosted factory install.

The loop

Eight steps, from signal to closed.

Three of them wait for you.

The Loams Software Factory loopEight stages in a ring: Signal, then Triage, then Plan, then Fix, then Review, then Deploy, then Observe, then Close, and back to the signal. Triage, Review and Deploy wait for a person.01Signal02Triage03Plan04Fix05Review06Deploy07Observe08CloseAgents do the legwork.You approve the merge.
Agent step Waits for you
  1. SignalAn error spikes in GlitchTip, or a metric dips in your product analytics.
  2. TriageYour callA thread opens in Zulip with the evidence. You reply "fix", "ignore" or "escalate".
  3. PlanAn issue appears in Plane, linked to the thread and the error.
  4. FixAn agent drafts a patch, opens a pull request in Forgejo, and runs CI. If CI fails, it tries again, up to three times.
  5. ReviewYour callYou review the diff and approve the merge in the console. The approval is recorded against your identity, and it expires.
  6. DeployYour callThe change rolls out through your GitOps pipeline.
  7. ObserveAgents watch errors, metrics, traces and LLM evaluations for the next 30 minutes.
  8. CloseFixed: the issue closes with a summary and what it cost. Regressed: a revert pull request opens, ready for your approval.
Loams Bot

One chat for every tool.

In the console, in a browser.

Ask in plain words: "Why did checkout errors spike after the 3 pm deploy?" or "Open an issue for it and draft a fix." Loams Bot asks the right agent in Zulip, Plane, Forgejo, GlitchTip or analytics, shows you each step as it happens, and hands you the approval when something needs a human. It runs in the console in your browser, and on the chat surface you connect it to.

  • Mention an agent with @plane, @zulip, @forgejo, @glitchtip or @analytics.
  • Every answer links to the real issue, thread, pull request or error.
  • Notifications open the exact thread or approval.
What you get

Built to be supervised, not trusted blindly.

Your tools, unmodified

Real Zulip, Plane and Forgejo, with single sign-on. Open the full app inside Loams or in your browser.

Agents with their own identity

Each agent has its own account, scoped permissions and a kill switch. No agent ever holds your passwords.

Human approval where it matters

Merging and deploying always wait for you, and every approval is recorded against your identity.

Budgets and limits

Set a budget per run and per day. Runs pause when they hit it.

A kill switch that always works

Stop one run, one agent or everything, from the console in your browser.

See every step

Open any agent step in Langfuse to see what the model saw and did, and in OpenObserve for the full trace.

A complete record

Every run keeps its thread, issue, pull request, deploy, cost and audit trail in one place.

Open standards

Agents talk over A2A, the Linux Foundation agent protocol. Bring your own model, or use ours.

The agents

Five agents and a chat.

Each has its own identity and only the skills it needs.

Plane agent

Issues and cycles

  • Search and read issues
  • Create, update and comment on issues
  • Summarise a cycle

Zulip agent

Streams and threads

  • Read threads
  • Open a triage thread with the evidence
  • Post and summarise

Forgejo agent

Repositories, pull requests and CI

  • Read pull requests, CI status and logs
  • Create branches and propose patches
  • Open pull requests

GlitchTip agent

Errors

  • Search errors and read events
  • List releases
  • Resolve or ignore an issue

Analytics agent

Product metrics

  • Query metrics
  • Read a funnel
  • Check for an anomaly (read only)

Loams Bot

Your chat

  • Routes your request to the right agent
  • Shows each step as it happens
  • Hands you the approval
Integrated apps

Real apps, run unmodified.

Run the same package yourself, or let Loams run it for you.

Plane, Zulip, Forgejo, GlitchTip, OpenPanel, Langfuse and OpenObserve are trademarks of their owners; Loams is not affiliated with them.

Security and approvals

Built to be supervised.

Gates

Merge and deploy need your approval. Reads are free; writes are logged.

Limits

Budgets, attempt caps, cooldowns and loop limits.

Control

Pause, kill and audit, from the console in your browser. Your data stays in your tenant.

Hosted tenants run in their own namespace with their own databases and bucket. We do not claim any compliance certification.

How you run it

Four ways to run the factory.

The loop is the same in all of them. What changes is who operates the stack and whose cloud it sits in.

  1. Run it yourself

    The 0.1.0 stack with Docker Compose, or one binary from source

    Released

    Start the v0.1.0 stack on your laptop and open it from the hosted console over your tailnet. Or build the engine and run it against a local directory, then point it at your bucket.

    • cargo run --release -p loams -- dev starts the native, Qdrant, Elasticsearch and Flight SQL listeners.
    • The default build adds Live on an embedded store; optional features add Durable, Graph, TiKV, SQL wire reads and stream gRPC.
    • Each release publishes Linux packages (Debian, RPM, Arch), macOS tarballs and a Windows zip for the loams CLI, and Loams Desktop installers. macOS builds are ad-hoc signed and Windows builds are unsigned.
    • Native desktop and mobile sources live beside the engine, with their own platform build and integration requirements.

    Build from source, or run the v0.1.0 images with Docker Compose. Loams 0.1.0 is the first release: APIs and formats may change between 0.x versions, and loams upgrade keeps your data.

    Run Loams 0.1.0Build from source

  2. Your cloud, your bucket

    Your VMs over your tailnet today; automated BYOC planned

    Over your tailnet

    Install the 0.1.0 stack on your own VMs over SSH and reach it only through your Tailscale tailnet, with the hosted console. The engine also runs standalone or in cluster mode against your bucket; a fully automated BYOC environment is the next layer.

    • Choose your object-store backend and protect the engine metadata and execution-state stores.
    • Use the scoped deployment and benchmark harnesses for their documented integration tasks.
    • The open control-plane design includes tenant isolation, Knative, Argo CD, Authentik and operator workflows.
    • Headscale networks and ephemeral provisioning remain planned; there is no automatic account-to-cluster install yet.

    Design Multitenant BYOC control plane

    Discuss a deployment

  3. Your own Cloudflare and Vercel

    Keep your application hosting; connect it to Loams on your compute

    Coming soon

    The intended setup keeps your application and the console on the hosting accounts you already use, and your data platform on compute you control. Deploying the console to your own Vercel or Cloudflare is coming soon; automated provisioning is still ahead.

    Local development

    Build the engine locally and connect your application to its documented API listeners.

    • Use the quickstart for a real engine and hybrid query.
    • The Loams 0.1.0 Compose stack and your Tailscale tailnet provide private connectivity today.
    Your cloud compute

    Run standalone or cluster mode on your own compute with your bucket.

    • Application hosting and engine storage remain independently chosen.
    • The BYOC design adds provisioning, tenant operations and private connectivity.

    Design Runtime and frontend hosting design

    Discuss this setup

  4. Design partnerships

    Work with us on your workload and deployment requirements

    By arrangement

    Bring a concrete AI workload, integration or self-hosted deployment requirement. We can review it against implemented capabilities and agree the engineering work needed for your environment.

    • Evaluate hybrid retrieval and protocol compatibility against your own data.
    • Explore reactive data, durable workflows, graph, analytics or agent integrations.
    • Review the public architecture, implementation evidence and release prerequisites.
    • Everything is open source; what we offer is services: support plans, SLAs, efficiency reviews and migration help, with scope and terms agreed directly.
    Become a design partner

The source engine runs today and Linux/Windows packaging is implemented. Stable publication, a complete setup bundle and automated private/BYOC provisioning are separate milestones. Design partnerships and custom deployments start at partnerships@ostriumlabs.org.

Install

From request to running loop in five steps.

  1. Request access and sign in
  2. Choose your deployment, region and model option
  3. Review what will be created and what each agent may do
  4. Wait a few minutes while Loams sets up your stack
  5. Connect a repository, invite your team and run the demo

Before anything is created you see the apps and their licences, the agents and what each may do, the budgets and default policy, and what is sent to the model provider. The hosted install is not open yet; the self-run Compose path is the one you can start with.

FAQ

Questions we expect.

Does it merge or deploy by itself?

No, never by default. You approve in Loams Bot or in the console, in your browser.

Which model does it use?

A model routed through the Loams gateway by default (DeepSeek at the moment). You can bring your own key.

Can I use my own Zulip, Plane or Forgejo?

The self-hosted open-source package connects your own. The hosted listing runs its own copies; connecting your own to the hosted plan is undecided.

What happens to my data if a deployment ends?

You export it before the environment is torn down. On the hosted listing the export window is 30 days; the self-run Compose path is yours to keep, in your own bucket.

Is it open source?

Yes, all of it, under Apache-2.0: the package, the agents, the apps’ integration and the chat. Loams has no open core. The hosted listing is the same code, run for you on Loams Cloud.

What does it cost to run a fix?

Each run shows its cost, and you set a budget per run and per day.

Do you train on my code?

We have not published a promise on this yet. It depends on our model provider’s terms, which we are confirming. Bring your own model key if you want to choose the provider yourself.

Which apps do I need to use?

None. The factory ships with its own.

Put the loop to work on your product.

Request early access with a Loams account. We will tell you when the hosted install opens. Prefer to run it yourself? The package is open source.

Request early accessBack to the marketplace