<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: donald_pinckney</title><link>https://news.ycombinator.com/user?id=donald_pinckney</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 30 Oct 2026 00:08:05 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=donald_pinckney" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Show HN: Sectr – Serverless backend platform for easy deployment of AI agents]]></title><description><![CDATA[
<p>Hey HN, I've been building Sectr, a backend-as-a-service for making it easy(ier) to develop and deploy AI agents. Deploying agents requires non-trivial systems design work. Consider a support agent: how do you stream messages to your frontend, how/where do you persist messages for frontend fetching later (or for auditing), and when the agent wants to issue a refund, do you spin-down the compute infra while it's waiting on human approval? Sectr aims to be the serverless abstraction and platform to provide these systems for you.<p>No sign-up needed to try using the dev server:<p><pre><code>  curl -fsSL https://sectr.dev/install.sh | sh # Install CLI
  sectr init my-agent && cd my-agent # Starter code
  sectr dev # Dev server, with UI to test chatting
</code></pre>
Sectr provides:<p>- Streaming of every token, tool call and event, and persistence so they can be loaded fresh later.<p>- Scaling up, and down to zero when the agent needs to wait, and resumption right to the suspended agent's state.<p>- Human approved tools automatically use Sectr's suspension and resumption capabilities, no code needed from you.<p>- AG-UI endpoint for any deployed agent so you can trivially hook up your frontend<p>- Local dev server experience, so you can rapidly debug and iterate on your agent's behavior<p>At the core, you can deploy any container image to Sectr as long as it implements a certain shaped HTTP endpoint. In practice, currently Sectr provides adapters to let you deploy your existing OpenAI Agents SDK, LangGraph, or Pydantic AI agents, with only 2 new lines of code:<p><pre><code>  app = AgentApp(name="support")
  app.add_route("/chat", openai_agents(agent))
</code></pre>
Certainly the hardest part of building Sectr was getting the resumption logic to be correct and invisible, across the Program State x Model Provider x Agent Framework matrix. For example, an earlier bug was when a model replied with text plus a tool call, Sectr would resume that as two separate messages, instead of one message with a text and tool part. This works, but breaks prompt caching (and might subtly change model behavior).<p>Sectr is free during the beta (and can be tried locally without sign-up); I mainly want feedback, especially on dev & deployment experiences, any bugs, and what features would excite you.<p>Introductory video: <a href="https://www.youtube.com/watch?v=H-y3wynkKc0" rel="nofollow">https://www.youtube.com/watch?v=H-y3wynkKc0</a><p>Docs: <a href="https://docs.sectr.dev" rel="nofollow">https://docs.sectr.dev</a></p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=50260969">https://news.ycombinator.com/item?id=50260969</a></p>
<p>Points: 5</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 27 Oct 2026 15:40:07 +0000</pubDate><link>https://sectr.dev</link><dc:creator>donald_pinckney</dc:creator><comments>https://news.ycombinator.com/item?id=50260969</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50260969</guid></item></channel></rss>