You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(landing/why): add server/daemon mode as coming soon pain
New pain: "Want agents running 24/7 on a server, not just locally"
Solution: orch serve — headless daemon, pm2/systemd compatible, REST API.
Updated counter: 10 solved, 3 in progress, 3 coming soon.
Also updated docs/ajtbd/05-jobs-pains-solutions.md with this pain.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@@ -364,10 +364,24 @@ <h1>Every pain we <em>already solve</em></h1>
364
364
</div>
365
365
</div>
366
366
367
+
<divclass="card missing">
368
+
<divclass="pain">
369
+
<divclass="card-label">Pain</div>
370
+
<divclass="card-title">Want agents running 24/7 on a server, not just locally</div>
371
+
<divclass="card-desc">You want to deploy ORCH to a VPS and have agents continuously process tasks — like a CI pipeline, but for AI work. Right now ORCH runs in your terminal and stops when you close it.</div>
<divclass="card-desc">Run ORCH as a persistent background process: <code>orch serve</code>. Watches for new tasks, dispatches agents, retries failures — headless, 24/7. Deploy on any VPS with <code>pm2</code> or <code>systemd</code>. REST API for external integrations.</div>
377
+
<divclass="card-tag">planned</div>
378
+
</div>
379
+
</div>
380
+
367
381
</div>
368
382
369
383
<divclass="bottom">
370
-
<h2>10 solved. 5 more <em>in progress.</em></h2>
384
+
<h2>10 solved. 6 more <em>in progress.</em></h2>
371
385
<p>ORCH already handles the hardest parts of multi-agent coordination — isolation, retry, state tracking, messaging. The rest is coming fast.</p>
372
386
<ahref="https://github.com/oxgeneral/ORCH#start-coordinating-agents-in-30-seconds" class="cta-btn">Try it on your project →</a>
373
387
<divclass="sub">MIT license · zero cloud · one npm install</div>
0 commit comments