From error to fix to deploy, in one loop you can stop.
Loams Software Factory connects Zulip, Plane, Forgejo, GlitchTip and your product analytics with AI agents, driven from one chat called Loams Bot on the native desktop app (Linux, macOS, Windows) and the native mobile apps (iOS, Android). Agents do the legwork. You approve the merge.
Early access. Loams Software Factory is in design and build. This page describes what it is designed to do, and the hosted install is not open yet. Requesting access creates a Loams account and holds your place.
Eight steps, from signal to closed. Three of them wait for you.
- SignalAn error spikes in GlitchTip, or a metric dips in your product analytics.
- TriageYour callA thread opens in Zulip with the evidence. You reply "fix", "ignore" or "escalate".
- PlanAn issue appears in Plane, linked to the thread and the error.
- FixAn agent drafts a patch, opens a pull request in Forgejo, and runs CI. If CI fails, it tries again, up to three times.
- ReviewYour callYou review the diff and approve the merge on your phone, with your fingerprint or face.
- DeployYour callThe change rolls out through your GitOps pipeline.
- ObserveAgents watch errors, metrics, traces and LLM evaluations for the next 30 minutes.
- CloseFixed: the issue closes with a summary and what it cost. Regressed: a revert pull request opens, ready for your approval.
One chat for every tool. On the native desktop app and the native mobile apps.
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 on the native desktop app (Linux, macOS, Windows) and the native mobile apps (iOS, Android).
- 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.
Illustration, not a screenshot
Why did checkout errors spike after the 3 pm deploy?
Asking @glitchtip and @forgejo. One new error, linked to the 3 pm release.
Open an issue for it and draft a fix.
Pull request ready. Waiting for your approval to merge.
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. Approvals are signed on your device.
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 your desktop or phone.
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.
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
Real apps, run unmodified. Run the same package yourself, or let Loams run it for you.
- ZulipTriage threads
Apache-2.0 - PlaneIssues and cycles
AGPL-3.0 - ForgejoCode, pull requests and CI
GPL-3.0-or-later - GlitchTipError tracking
MIT - OpenPanelProduct analytics, an add-on
AGPL-3.0 - LangfuseLLM traces and evaluations
MIT, except ee/ - OpenObserveLogs, metrics and traces
AGPL-3.0
Plane, Zulip, Forgejo, GlitchTip, OpenPanel, Langfuse and OpenObserve are trademarks of their owners; Loams is not affiliated with them.
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 your desktop or phone. Your data stays in your tenant.
- Text from apps (issue bodies, chat messages, error messages) is untrusted data, and no action is chosen on it alone without the policy gate.
- A destructive call needs a settled approval that matches the call, so an agent that skips the gate still cannot get the credential.
- The person who requested a change cannot approve it, and approvals time out after 72 hours.
- The conservative default policy ships on: gates on, auto-fix off.
Hosted tenants run in their own namespace with their own databases and bucket. We do not claim any compliance certification.
Plans, with the model cost visible. Numbers are placeholders until launch.
Starter
$XX/ month
Included
- 1 project, 3 people
- N runs a month
- T model tokens a month
Model
- Managed, or bring your own key
Beyond the plan
- Extra runs: $X per run
- Extra tokens: provider cost plus X%
- Product analytics (OpenPanel): $XX / month
14-day trial planned
Team
$XXX/ month
Included
- 5 projects, 15 people
- 3N runs a month
- 3T model tokens a month
Model
- Managed, or bring your own key
Beyond the plan
- Extra runs: $X per run
- Extra tokens: provider cost plus X%
- Product analytics (OpenPanel): $XX / month
14-day trial planned
Business
Contact us
Included
- Custom projects and people
- SSO groups
- Longer audit retention
- Priority support, BYOC option
Model
- Managed, bring your own key, or a private model route
Beyond the plan
- Custom runs and tokens
- Product analytics included
Pilot
Placeholder prices: the numbers are set before launch. Prices exclude tax. Model usage beyond the allowance is billed at cost plus a margin. Bring your own key and pay only the provider.
From request to running loop in five steps.
- Request access and sign in
- Choose your plan, region and model option
- Review what will be created and what each agent may do
- Wait a few minutes while Loams sets up your stack
- 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.
Questions we expect.
Does it merge or deploy by itself?
No, never by default. You approve in Loams Bot, the console or your phone.
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 I cancel?
You can export it for 30 days; then it is deleted.
Is it open source?
Yes: the package, the agents, the apps’ integration and the chat are open. The hosted service, billing and managed models are 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.