<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Zero-Idle on Prosyon Research</title><link>https://research.prosyon.ca/topics/zero-idle/</link><description>Recent content in Zero-Idle on Prosyon Research</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 31 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://research.prosyon.ca/topics/zero-idle/index.xml" rel="self" type="application/rss+xml"/><item><title>Zero-Idle</title><link>https://research.prosyon.ca/definitions/zero-idle/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://research.prosyon.ca/definitions/zero-idle/</guid><description>&lt;p&gt;Zero-idle is the primary cost constraint governing Prosyon system design. Every architectural choice is evaluated against whether the system can reach $0 at idle — where &amp;ldquo;idle&amp;rdquo; means no incoming traffic and no scheduled work.&lt;/p&gt;
&lt;p&gt;The practical implication is a preference for pay-per-request primitives (Lambda, DynamoDB on-demand, CloudFront, S3) over always-on resources (EC2, RDS, NAT Gateways). A zero-idle system may still have a small storage cost at rest, but compute and transfer costs trend to zero.&lt;/p&gt;</description></item></channel></rss>