← All concepts

deployment patterns

29 articles · 15 co-occurring · 1 contradictions · 6 briefs

living on your computer migrating into my personal server soon" — LettaBot is deployed as local-first software running on personal infrastructure

@petergyang: Was 2025 really the year of AI agents or more like the year of AI agent hype?

[INFERRED] "Was 2025 really the year of AI agents or more like the year of AI agent hype?" — Author questions whether 2025 represented genuine AI agent adoption or merely marketing hype. This challenges optimistic narratives about agent deployment maturity and suggests gap between claims and actual implementation.

2026-W15
140
2026-W14
1

living on your computer migrating into my personal server soon" — LettaBot is deployed as local-first software running on personal infrastructure

Flexible deployment options for local and remote scenarios. Reuse your MCP server across different tools and platforms." — Establishes MCP's multi-platform deployment flexibility as a core benefit

we've been hitting all sorts of new bottlenecks: code review and regression prevention, CI and merge queues, source control reliability, etc." — Identifies specific infrastructure bottlenecks emerging

We just shipped support for running @Letta_AI agents inside Daytona sandboxes" — Letta agents running in Daytona sandboxes is a concrete deployment pattern combining containerized execution with state

Capital One built multi-agent workflows to support enterprise use cases, embedding agents directly into operational systems rather than isolating them in labs" — Capital One case demonstrates real-wor

success requires focusing more on the "sociotechnical" aspects of implementation and infrastructure instead of more expected tasks such as prompt engineering" — Article identifies sociotechnical aspec

Letta Code transports agents (regardless of origin) to the local machine it's running on" — Demonstrates practical agent portability - agents can be deployed/moved to different machines on demand

for no particular reason, a new kimi comes out and I have to self-host it and poke around with it. I have to feel the power of running such a great model myself" — Demonstrates self-hosted inference p

Claude Code on Android" — Claude Code's availability on Android demonstrates platform expansion of AI coding assistance beyond desktop environments, enabling on-the-go code development.

[direct] "slopforked the @opencode server so it runs entirely inside a @CloudflareDev Durable Object" — Demonstrates deploying a server application on Cloudflare's edge infrastructure without traditio

[direct] "drop $20k on new hardware to run local models" — Article demonstrates concrete cost and infrastructure requirements for running local models independently

so you can start one up on-demand to handle one AI chat message and then throw it away" — On-demand ephemeral execution model for individual requests represents efficient resource utilization pattern

rolling back fixes to make things more stable" — Demonstrates proactive rollback strategy to mitigate production risks during critical period (holidays)

[INFERRED] "Was 2025 really the year of AI agents or more like the year of AI agent hype?" — Author questions whether 2025 represented genuine AI agent adoption or merely marketing hype. This challeng

[high] "One-click deploy template" — Exemplifies simplified infrastructure deployment pattern using Railway one-click templates for Claude Code server setup

MCP servers are programs that run on your computer and provide specific capabilities to Claude Desktop" — Article describes the local deployment model where MCP servers execute on user's machine, exem

We will handle the containers, local certs, etc" — Automated container management is a key value proposition of railway dev

the paper decided to release the product anyway, saying it would "iterate through the remaining issues"" — Real-world example of deploying AI product with known critical flaws under assumption of post

Hire (or become) agent SRE specialists. This capability is defensible because it's operationally hard." — Article provides evidence that operational reliability and deployment expertise for agents is

Run Online Evaluations periodically on live traffic to detect regressions in response quality" — Article provides concrete evidence that online evaluation is a critical practice for monitoring agent q

[INFERRED] "all powered by workers ai (or byom)" — Article demonstrates serverless agent architecture pattern using Cloudflare Workers and model choice flexibility (bring-your-own-model)

Building a PWA for Pi coding agent" — PWA running on Raspberry Pi demonstrates local/edge deployment of an AI coding agent without cloud dependency.

[INFERRED] "A sign of a path forward for agents that will not terrify corporate IT." — Article suggests Claude Cowork adds a new dimension to enterprise agent deployment by addressing IT security conc

[DIRECT] "you can now deploy websockets based discord bots to cloudflare workers" — Announces a new deployment capability: Discord bots can now run on Cloudflare Workers via websockets gateway access

[INFERRED] "Set it up in one click, and use your ChatGPT subscription (or any other API key.)" — Plus One demonstrates one-click agent deployment reducing infrastructure friction

[INFERRED] "start shipping terraform providers" — Author advocates terraform providers as the preferred pattern for shipping and deploying tooling, treating infrastructure definition as the canonical

[INFERRED] "im one of them" — First-person account of Claude being used in active development at Waymo, indicating real-world deployment of AI coding assistants in autonomous vehicle development

[INFERRED] "By 2026, 40% of enterprise applications" — Article cites enterprise adoption metrics for multi-agent systems, providing evidence of industry-wide adoption trends.

[inferred] "Claude runs it via cloud infra on your schedule, so you don't need to keep Claude Code running on your local machine" — Describes cloud-based task scheduling as alternative to local infras

query this concept
$ db.articles("deployment-patterns")
$ db.cooccurrence("deployment-patterns")
$ db.contradictions("deployment-patterns")