2026-04-02T20:10:23Z https://nostr.ae rajesh https://nostr.ae/npub1hv288dxp0a5emsptlsnu5cw496mgh4l8suzfndkvuruxzfr8909sdqkqdn https://media.medampudi.com/f14f857a2a5cf4fa08753a3079e45a2142dd50eccf1928dd877ee0272ea6cab8.png https://media.medampudi.com/f14f857a2a5cf4fa08753a3079e45a2142dd50eccf1928dd877ee0272ea6cab8.png https://nostr.ae/nevent1qqswe5wz2w2a99pr7ykwqujp8hs3062d6xmhyxf8xc8xrrxw4jurseczyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uknr69cm two questions decide whether you write an s3 lifecycle policy or hand it to intelligent-tiering, and most people skip both.<br/><br/>do you know the access pattern? logs cold after 30 days, backups after 90 — if you know, write the policy and s3 moves the data on a schedule. if you don&#39;t know — user uploads, a data lake, hot and cold mixed unpredictably — that&#39;s exactly what intelligent-tiering is for.<br/><br/>second question: are the objects big enough and not billions of them? if they&#39;re tiny or short-lived, neither pays off, stay in standard. and if you do write a policy, set Expiration — storage you delete is storage you stop paying for forever, and it&#39;s the most underused line in s3.<br/><br/><a href="https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook">https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook</a><br/> <img src="https://media.medampudi.com/33f34908218d7f453df0248d9fa8b89ed58a5e7dadd141a9da5bbcabaafb1339.png"> 2026-07-15T17:37:02Z https://nostr.ae/nevent1qqsqunjawegm3h7h8e5ts8tm0vhfjepac7xzasy7ugtsfzy8v6ven4szyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uknkd7pw give me read access to a $50k/mo AWS bill and i&#39;ll show you where the first fifth is hiding. usually the same four places.<br/><br/>i&#39;ve run this enough that the pattern is boring. data transfer nobody instruments, boxes sized for a load test two years ago, on-demand on a baseline that never moves, storage rotting in the priciest class.<br/><br/>the audit isn&#39;t a pitch before the work. the audit is the work.<br/><br/><a href="https://rajesh.medampudi.com/blog/audit-50k-aws-bill">https://rajesh.medampudi.com/blog/audit-50k-aws-bill</a><br/> <img src="https://media.medampudi.com/1b9f04c74bbfc9151469e28255c26601e0296c1eb9bc91ae35f127abd4f22f59.png"> 2026-07-15T09:37:02Z https://nostr.ae/nevent1qqsqhzrlapgya0nane4dw5yn4jsmd594ywh7ffrfwfq934lnq4a9tjszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukesztz0 showback before chargeback. the order matters more than people think.<br/><br/>showback shows each team its slice of the bill with no money attached. chargeback moves the cost onto its budget. lead with chargeback and you get a turf war — teams litigate the allocation instead of fixing the waste.<br/><br/>most over-spend isn&#39;t malice, it&#39;s invisibility. show a team its number and a real fraction self-corrects before anyone enforces anything. order of operations: inform, then showback, then chargeback for the stubborn remainder. start at the bottom.<br/><br/><a href="https://rajesh.medampudi.com/blog/infra-bill-as-product-metric">https://rajesh.medampudi.com/blog/infra-bill-as-product-metric</a><br/> <img src="https://media.medampudi.com/b912e8d310f46bb47dd7b371997ffc7dad0923952bd31afc42ec634562a4cf66.png"> 2026-07-14T17:37:02Z https://nostr.ae/nevent1qqs9dfc702ws3ptxx4g9v9ua6gdyuu7ay6py0us68yc58cu80nac67czyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk9rkufh the whole &#34;RIs or savings plans?&#34; decision routes in two questions.<br/><br/>is it redshift or opensearch? → reserved node / reserved instance. no savings plan exists. done. is it another managed database — rds, aurora, elasticache, dynamodb and the rest? → database savings plan, 1-year no upfront, for steady-state.<br/><br/>otherwise it&#39;s ec2/fargate/lambda: compute SP for flexibility, ec2 instance SP for the deepest rate, a reserved instance only if you need a capacity guarantee in an AZ or a resale exit. everything else → compute SP, the safe default.<br/><br/><a href="https://rajesh.medampudi.com/blog/ri-vs-savings-plans">https://rajesh.medampudi.com/blog/ri-vs-savings-plans</a><br/> <img src="https://media.medampudi.com/867f02b20e4e550ffc58c6100359f21580907c25f8cd7b03c729d58f72b1138a.png"> 2026-07-14T09:37:02Z https://nostr.ae/nevent1qqsr7t9jlmmwdwsxwutztlwzxwdsf4ctlazv267hxhdzntwcrt5r4cczyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk78cmun before you fix anything, measure. fifteen minutes in cost explorer tells you whether this is a $30 problem or a $3,000 one.<br/><br/>group by usage type. NatGateway-Hours is your fixed cost, number of gateways times hours — not much to chase there. NatGateway-Bytes is the one worth chasing.<br/><br/>then turn on vpc flow logs and see where those bytes go. if a large share is heading to s3, ecr, or dynamodb, that&#39;s spend you can zero out with a route-table edit. don&#39;t optimise on a hunch.<br/><br/>#aws #cloudcost<br/><br/><a href="https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax">https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax</a><br/> <img src="https://media.medampudi.com/a4f409c5c5547e95a656d84443c83d6b36e98a0c6f52f5346c179bc39d652525.png"> 2026-07-13T17:37:02Z https://nostr.ae/nevent1qqs089gtzm8hzuepct4prewtsdpf5qcfskptyzaaktjtvk0dcjqul8szyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukk79tvd free s3 win almost everyone leaves on the table.<br/><br/>if your EC2/ECS/lambda in a VPC talk to s3, by default that traffic leaves through a NAT gateway — which bills an hourly charge plus per-GB data-processing on every byte. pulling terabytes from s3 that way is a tax you&#39;re paying for nothing.<br/><br/>an s3 gateway VPC endpoint routes the same traffic privately for $0. no hourly, no per-GB, no transfer charge for same-region s3. one route-table edit. caveat: it only covers same-region VPC-to-s3 — on-prem, cross-region or transit-gateway paths need the paid interface endpoint. for the common case you should&#39;ve created it on day one.<br/><br/><a href="https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook">https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook</a><br/> <img src="https://media.medampudi.com/e9ebd4d8469fd412af7e69cea7bc1bf7a8399c65af6e4a2f66b854878424cafe.png"> 2026-07-13T09:37:02Z https://nostr.ae/nevent1qqstuz48s8dzy2zmuqucjuzwdan4gllnxktsc342hpt5ntjdgvaa4dszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukh20gj2 the most expensive AWS mistake isn&#39;t paying on-demand. it&#39;s locking in a multi-year commitment on a fleet you&#39;re about to halve.<br/><br/>the gate is simple. fleet rightsized? if no, resize first — don&#39;t commit. stable baseline? if yes, buy the compute savings plan, up to 66% off, sized to that baseline.<br/><br/>a smaller baseline buys a cheaper, more accurate commitment. that&#39;s why the order matters.<br/><br/><a href="https://rajesh.medampudi.com/blog/audit-50k-aws-bill">https://rajesh.medampudi.com/blog/audit-50k-aws-bill</a><br/> <img src="https://media.medampudi.com/6a1d140d1d3f107259f3423330bc6828d61f4d2b03c40404b8ddafb0e808ce77.png"> 2026-07-10T17:37:02Z https://nostr.ae/nevent1qqsqpk3jyyg3xt4yqxwfznckeryyyt26nk03sjlxedryqldpd0arz6gzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukuknggr a metric that lives in a monthly finance review is not a metric anyone who moves it ever sees.<br/><br/>the cost of a code path is a property of that code path, same as its latency. so put cost per request on the same grafana board as latency. same screen, same on-call engineer.<br/><br/>an engineer who sees a new endpoint costs 4x per call fixes it in the PR, context hot, for the price of a code review. the same regression caught six weeks later in a finance reconciliation is a forensic investigation. same bug. timing decides the fix cost.<br/><br/><a href="https://rajesh.medampudi.com/blog/infra-bill-as-product-metric">https://rajesh.medampudi.com/blog/infra-bill-as-product-metric</a><br/> <img src="https://media.medampudi.com/cecf5dccb2ead8cf0001dc5a3a0fc5190dda76408d4ef6c96c7279e34ecdc281.png"> 2026-07-10T09:37:03Z https://nostr.ae/nevent1qqs92xjvgymnl20pc8zxrhsery0nye60t92dxkv62c7g6fn05xqm8dczyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukm04y0a worth noticing: aws now recommends savings plans over reserved instances for compute. the vendor selling you the RI is telling you to buy the other thing.<br/><br/>the logic is clean. the convertible RI exists for flexibility — the compute SP does that better, automatically, no manual exchanges. the standard RI exists for the deepest rate — the ec2 instance SP matches the 72% and stays flexible inside the family.<br/><br/>both reasons the RI existed for ec2 are now done better by a savings plan. that&#39;s why the recommendation flipped.<br/><br/><a href="https://rajesh.medampudi.com/blog/ri-vs-savings-plans">https://rajesh.medampudi.com/blog/ri-vs-savings-plans</a><br/> <img src="https://media.medampudi.com/106caa05673e1f22154f74fea930693759dec7e634609445090de724d892e09b.png"> 2026-07-09T17:37:02Z https://nostr.ae/nevent1qqszldrcfed44vkf0d7ha47xzjmmf6nzshynhwvrc8llta85nqtwt0czyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukd7xre7 cutting a nat bill, the order matters more than any single fix, because the cheap no-downside moves capture most of the money.<br/><br/>s3 + dynamodb gateway endpoints — free, one route-table edit. start here.<br/>interface endpoints for ecr and logs — $0.01/GB, under a quarter of nat&#39;s rate. cheap, but do the per-service math.<br/>cross-AZ cleanup, and the honest question of whether the subnet needs nat at all.<br/>fck-nat — real savings, but no default failover and a patching burden. last resort.<br/><br/>most teams never get past step two.<br/><br/>#aws #infrastructure<br/><br/><a href="https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax">https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax</a><br/> <img src="https://media.medampudi.com/fe1fcb6aff2cf82aceb738151e99359921a3a0f88387d442d119de9c70b40d89.png"> 2026-07-09T09:37:02Z https://nostr.ae/nevent1qqs0djrne2t7k53c5xruykfmqy4fzlj2v6lyjtyrccn3nxkhklcvvkqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukkj207t the order isn&#39;t decoration. each decision makes the next possible.<br/><br/>cut the waste first — free, mostly attention not architecture. then own past your break-even (datadog past my line → built it ~8x cheaper on LGTM). then observe cheaply, because you can&#39;t decide the first two without numbers. then staff light. i run all four — k8s, self-hosted observability, the services on top — alone, from a modest house in hyderabad. the load is far lower than the staffing story implies.<br/><br/><a href="https://rajesh.medampudi.com/blog/what-lean-infrastructure-means">https://rajesh.medampudi.com/blog/what-lean-infrastructure-means</a><br/> <img src="https://media.medampudi.com/c95edc690ffc1a48ebfca479d963396f3a5dd1392e01cc3dec514e40e751b38e.png"> 2026-07-08T17:37:02Z https://nostr.ae/nevent1qqs2t7wvgn4quapmf3nkpfwe94t8wphsmlq0nqrhvyx0xy3m29xh82gzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk8welmn there&#39;s storage on your s3 bill you can&#39;t see in the console and you&#39;re paying for it right now.<br/><br/>upload a big object in parts, the upload fails partway — dropped connection, crashed job, sdk that didn&#39;t clean up — and the parts that landed stay in the bucket. you get billed for them. they don&#39;t show in the object listing. they pile up for years.<br/><br/>the fix is one lifecycle rule on every bucket: AbortIncompleteMultipartUpload, 7 days. applies to existing + future uploads, and per aws it doesn&#39;t trigger early-delete charges. no downside. set it today before you touch anything else — cheapest win in the whole thing.<br/><br/><a href="https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook">https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook</a><br/> <img src="https://media.medampudi.com/fb3ce950d9a5b69530f225814c7fdd772ba75a713109dce3be771c06d9245722.png"> 2026-07-08T09:37:02Z https://nostr.ae/nevent1qqs2kqqpfwwxehzln9v4jfcrgse8ltecu96pmd3wtqrzwfv3tthsu7qzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk7de7vq before you buy a single savings plan, sweep the free money. none of it needs a commitment and all of it is just sitting there.<br/><br/>unattached EBS volumes still billing. old snapshots nobody deletes. idle public IPv4 — $0.005/hr each since feb 2024, attached or not. and untagged spend, because you can&#39;t cut what you can&#39;t see.<br/><br/>clean the dead weight first. then size the commitment to a real baseline.<br/><br/><a href="https://rajesh.medampudi.com/blog/audit-50k-aws-bill">https://rajesh.medampudi.com/blog/audit-50k-aws-bill</a><br/> <img src="https://media.medampudi.com/52e881edf6c6496cf1ea5d208c555354b5c3ad0fefbee4bc74b07b3406ed5b3a.png"> 2026-07-07T17:37:02Z https://nostr.ae/nevent1qqs09cg8wc4mtp88f7jca42jy6rsuaqjl7qnxknz4zs8my4xarzs3rqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukmh4tm3 total dollars on a bill lie, and here&#39;s exactly how.<br/><br/>the signal arrives weeks after the decision that caused it. it lands in front of finance, who can read it but can&#39;t fix it. the engineer who can fix it never sees it. and total $ can&#39;t tell a bill that doubled on growth from one that doubled on waste.<br/><br/>four failures, all structural. divide into a per-unit number and all four fix at once — timely, actionable, owned by the right person, and it tells growth from waste at a glance.<br/><br/><a href="https://rajesh.medampudi.com/blog/infra-bill-as-product-metric">https://rajesh.medampudi.com/blog/infra-bill-as-product-metric</a><br/> <img src="https://media.medampudi.com/8413e1805c253a74e08b91eea5a034217055f472bb16d6ec664326741585818e.png"> 2026-07-07T09:37:02Z https://nostr.ae/nevent1qqsyc5lvaa6dzkvg3rzeltjkfl3755kurn094nhqueppnnuzatzexdqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukme7cfc on 2 december 2025 aws finally launched database savings plans — the gap that kept most database spend stuck on reserved instances for years.<br/><br/>covers aurora, rds, dynamodb, elasticache, documentdb, neptune, keyspaces, timestream and dms. up to 35% on serverless, 20% on provisioned, and it follows the workload across engine, family, size and region.<br/><br/>two catches worth saying out loud: it&#39;s 1-year no-upfront only at launch, and it does NOT cover redshift or opensearch — i&#39;ve already seen that stated wrong. check the official service list.<br/><br/><a href="https://rajesh.medampudi.com/blog/ri-vs-savings-plans">https://rajesh.medampudi.com/blog/ri-vs-savings-plans</a><br/> <img src="https://media.medampudi.com/6290713b4b767b36083f722f9605d173a09a14665c0e548b14b3490616cb308a.png"> 2026-07-06T17:37:03Z https://nostr.ae/nevent1qqsqkk33vt7ar6ecp5s4lv2jewyvl0lfzwqv8y43zuq2j2naf3xwc0szyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk9kd4nk four signs your nat gateway is doing a job a free endpoint should be doing: s3 reads from private subnets, ecr image pulls on every deploy, a nat sitting in a different AZ than your workloads, and one nat carrying multiple terabytes a month.<br/><br/>you don&#39;t have to guess. turn on vpc flow logs for the nat&#39;d subnets and look at where the bytes go. a big share heading to s3, ecr, or dynamodb is the smell — and the cheapest fix you&#39;ll find this quarter.<br/><br/>#aws #devops<br/><br/><a href="https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax">https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax</a><br/> <img src="https://media.medampudi.com/578b5a8b735f7b0f79f976f722a28935fe0d566b4548bc929e2cc1ef20e2f53f.png"> 2026-07-06T09:37:03Z https://nostr.ae/nevent1qqszezs4audn2jdc7gx82fzjt5m7xx2a30qhdpe05djl4xwx3sl8ffszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk69j9fg people hear &#34;lean&#34; and think &#34;cheap.&#34; it&#39;s the opposite.<br/><br/>cheap is cutting the thing that matters to save a small number — you win a line item and lose the business. lean is spending deliberately on what actually buys you something, so you have room to do the work that moves the business. the point of cutting a $120K/mo observability bill was never the $120K. it was no longer being held hostage by it.<br/><br/><a href="https://rajesh.medampudi.com/blog/what-lean-infrastructure-means">https://rajesh.medampudi.com/blog/what-lean-infrastructure-means</a><br/> <img src="https://media.medampudi.com/48b5d0bd39ae2fd2acd61be99460b98da1c31178256118e58b2a6dbebb8ccb0b.png"> 2026-07-03T17:37:02Z https://nostr.ae/nevent1qqs0tesgtq2nyhhtg9uzuesvgm5myghr37uvmqycnc658t6aufden5czyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukpnztk8 how a $120K/mo observability bill quietly happens: three systems billing at once. datadog the official tool. cloudwatch still alive underneath that nobody turned off. and engineers SSHing into boxes to grep logs during incidents because paid search was too slow to trust.<br/><br/>none of them complete, all of them on the meter, spend climbing 15%/mo. the fix isn&#39;t clever — one stack you own: grafana LGTM backed by s3, on your own kubernetes, data stays yours. costs become compute + storage, which scale slow. no vendor between you and the 3am fix. one bill you can actually read.<br/><br/>#infrastructure #cloudcost #selfhosting<br/><br/><a href="https://rajesh.medampudi.com/blog/observability-cost-kill">https://rajesh.medampudi.com/blog/observability-cost-kill</a><br/> <img src="https://media.medampudi.com/4c5f790130f016a44a40e7b9b777c8e4020009ec21c33c66c606757d9f06d03a.png"> 2026-07-03T09:37:02Z https://nostr.ae/nevent1qqstcr8grpjuk33yz3c3ycj2qlyue08wa7hsy9uqeunm3ska0x589cgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk82903h the trap that quietly reverses your s3 savings: standard-IA, one zone-IA and glacier instant all bill every object as if it were at least 128KB.<br/><br/>so you take a bucket of 10KB thumbnails, move it to a &#34;cheaper&#34; class to save money, and now each object bills at 128KB. you&#39;re paying for ~12x the bytes you actually store. the per-GB label looked cheaper, the bill came back higher.<br/><br/>small objects stay in standard. check your average object size before tiering anything down — under 128KB and IA is just wrong, no matter how cold the data is.<br/><br/><a href="https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook">https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook</a><br/> <img src="https://media.medampudi.com/3af0ba4769d6f20212edfc5d130ee400bcfeb98db854620cccae3ecc582644ba.png"> 2026-07-02T17:37:02Z https://nostr.ae/nevent1qqstw80ly9awvqezekvsymshcyz34x5796qygtcwz9lq7khq2hgfrwqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukj60p7s give me read access to a $50k/mo AWS bill and i&#39;ll find the first 20-30% in a day. not clever — it&#39;s always the same four places, same order.<br/><br/>data transfer → rightsize → commit → storage cleanup.<br/><br/>the order is the whole thing. each step makes the next one cheaper. don&#39;t commit before you rightsize, don&#39;t rightsize a fleet still leaking free traffic through a paid NAT. run it bottom to top.<br/><br/><a href="https://rajesh.medampudi.com/blog/audit-50k-aws-bill">https://rajesh.medampudi.com/blog/audit-50k-aws-bill</a><br/> <img src="https://media.medampudi.com/fbfa54a6a72776daf71bc14f3d809ab5dc315f246baf3b043324ba44be99cc48.png"> 2026-07-02T09:37:03Z https://nostr.ae/nevent1qqsrusqfqe00q85gf3c4zah3f5cd0njr3vzler2rd7mvvqsy4yqa89qzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukq6udsq the whole unlock is dividing.<br/><br/>total infra cost over requests = cost per request. over tenants = cost per tenant. the finops foundation calls it unit economics. the arithmetic is trivial. the shift it forces is not.<br/><br/>two buckets worth keeping separate: resource-efficiency (cost per GB, per vCPU, per token) tells you how the machinery is wasting. business metrics (cost per tenant, cost to serve) tell you whether it matters. once cost is per-unit, a rising bill stops being scary by default.<br/><br/><a href="https://rajesh.medampudi.com/blog/infra-bill-as-product-metric">https://rajesh.medampudi.com/blog/infra-bill-as-product-metric</a><br/> <img src="https://media.medampudi.com/f0a2a892befca3dbce052749842d659326fc732e5331af05ce9cd44110d722a0.png"> 2026-07-01T17:37:03Z https://nostr.ae/nevent1qqs02695sjkwvllqz2v8kaeg3q4835u8ld623szx4uaugyxheghf2dczyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk9f4nnc savings plans are the default now, but not the answer to everything. there are exactly three corners where the reserved model is still the only lever you have.<br/><br/>redshift uses reserved nodes, opensearch uses reserved instances — no savings plan covers either, even after the dec 2025 launch. a zonal RI reserves capacity in a specific AZ; a savings plan reserves none. and a standard RI can be sold on the marketplace; a savings plan can&#39;t be cancelled mid-term.<br/><br/>everything outside those three → savings plan.<br/><br/><a href="https://rajesh.medampudi.com/blog/ri-vs-savings-plans">https://rajesh.medampudi.com/blog/ri-vs-savings-plans</a><br/> <img src="https://media.medampudi.com/50cd1bf2b44060836666e028d1b4be3b5d505a137c898f3a384c8616042d211f.png"> 2026-07-01T09:37:02Z https://nostr.ae/nevent1qqswa2e6tn7we4ev4fzznj5x2g78tg7542fmcx2cxdsgr7yzz5wfj3gzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk4q6d9p the most common reason a nat gateway bill creeps: s3 reads from private subnets going out through nat at $0.045/GB.<br/><br/>the fix is free and almost nobody does it first. gateway endpoints for s3 and dynamodb cost nothing — no hourly fee, no per-GB fee. you add a route, and that traffic goes over a private aws path instead of through the meter. it never touches nat again.<br/><br/>do this before anything fancier. most teams never need to go further.<br/><br/>#aws #cloudcost<br/><br/><a href="https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax">https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax</a><br/> <img src="https://media.medampudi.com/fb94d6dc380dd2dc3a6d29d8189aa815d8ac91e3fa6cfc351706e18bc03dd332.png"> 2026-06-30T17:37:02Z https://nostr.ae/nevent1qqs8fgmv075wyvy4n6qs39eyjhthvamw9ljjkmk9r929l4un0nmjvdqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukwdd2r8 a fifth of enterprise cloud spend — ~$44.5B in 2025 — goes to resources nobody is using (harness, finops in focus 2025).<br/><br/>that&#39;s not carelessness. it&#39;s the default state of a bill nobody is actively cutting. idle instances, commitments bought on a guess, storage that should&#39;ve aged into a cheaper tier months ago. assume you&#39;re overspending — the data says you are — and go look once a month. you&#39;ll find the leak.<br/><br/><a href="https://rajesh.medampudi.com/blog/what-lean-infrastructure-means">https://rajesh.medampudi.com/blog/what-lean-infrastructure-means</a><br/> <img src="https://media.medampudi.com/bf3b3b0a7b4ea55698a22ea374ac3976ac7a61d18f189366ae7655ffdff5f344.png"> 2026-06-30T09:37:03Z https://nostr.ae/nevent1qqsyax7kkaqyt28a4m7jlydkyxpm9ffjssvc9jx4xxzydvqqdgqu2jqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk2zszyv the stack that replaced the saas bill, and it&#39;s boring on purpose: loki for logs, mimir for metrics, tempo for traces, grafana for dashboards + LogQL. running on our own kubernetes, 50+ nodes, 200 services, all backed by s3 underneath.<br/><br/>two surprises: log search was faster than the paid tool, and with no per-seat cost 15 teams onboarded in month one instead of rationing licences. we ran it in parallel with the old tooling for a full month before decommissioning anything — you don&#39;t pull monitoring during a tournament with 100k players online and hope.<br/><br/>#observability #grafana #kubernetes<br/><br/><a href="https://rajesh.medampudi.com/blog/observability-cost-kill">https://rajesh.medampudi.com/blog/observability-cost-kill</a><br/> <img src="https://media.medampudi.com/c2d867877ab5ecc80c0dffc68656b2b8ad0b5fc87438d2de5d39c860c3412b46.png"> 2026-06-29T17:37:02Z https://nostr.ae/nevent1qqs8nqh2xtr6gh4mves35zrxgkdg6lurrs32swwkusjpy09qgw6fy9czyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukjpzxaf s3 storage classes span a ~23x price range and the only thing separating them is access pattern. same bytes — standard is $0.023/GB-month, deep archive is about $0.00099.<br/><br/>most bills sit entirely in standard because that&#39;s the default and almost nobody changes it. it&#39;s the most expensive, most available class aws sells, tuned that way on purpose.<br/><br/>frequently read → standard. occasional + over 128KB → standard-IA. rarely read but instant → glacier instant. archive you can wait on → flexible. compliance you&#39;ll never read → deep archive. that&#39;s the whole call.<br/><br/><a href="https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook">https://rajesh.medampudi.com/blog/s3-cost-optimization-playbook</a><br/> <img src="https://media.medampudi.com/a885260c7f019899e98ec280b73abe27f96c9e2cecf748f7d2fb3eb9bc8d5407.png"> 2026-06-29T09:37:03Z https://nostr.ae/nevent1qqs975x2ydpmdtplwg7c7k5wckzcyp5zkz9grvny9wdrmlt3alzfyeszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk4pf2dq the most wasteful line on a mid-size AWS bill is the one with no resource page: data transfer.<br/><br/>the NAT gateway is the worst of it. $0.045/GB just to process traffic — and most teams route S3 + package pulls straight through it. a VPC gateway endpoint carries that same traffic for $0. one route-table edit.<br/><br/>i check this on every account. it&#39;s almost always there.<br/><br/><a href="https://rajesh.medampudi.com/blog/audit-50k-aws-bill">https://rajesh.medampudi.com/blog/audit-50k-aws-bill</a><br/> <img src="https://media.medampudi.com/71089fbc78a49523e903b0778baa8c8e5debfa9a53ce0c602429b2c996b402eb.png"> 2026-06-26T17:37:03Z https://nostr.ae/nevent1qqs9kjgv4szc44gkl2nlhlgsvyhxlmewr8jtg08haecxqvq0q9j0n0szyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk8g6tmk the cloud bill is the only production number most teams don&#39;t own until it&#39;s already a fire.<br/><br/>engineering owns latency. finance owns the invoice. nobody owns the gap — and a fifth to a third of cloud spend dies in it.<br/><br/>stop treating the bill as an accounting artifact. treat it as a product metric: cost per request, per tenant, per feature, on the same dashboard as latency. we already run every other signal this way. cost is the one we still run like a 1990s expense report.<br/><br/><a href="https://rajesh.medampudi.com/blog/infra-bill-as-product-metric">https://rajesh.medampudi.com/blog/infra-bill-as-product-metric</a><br/> <img src="https://media.medampudi.com/17ecf773fcde095c0b149f9ba94100ba012e773c16e8be4e5e6511d4677c2ebd.png"> 2026-06-26T09:37:02Z https://nostr.ae/nevent1qqszz722phn0fvve9ytg7twylm2dkvaayl4c3actjcc6dk52a8g6rsgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukjt8d77 for ec2 in 2026 the reserved instance is the legacy choice, and most people are still running the old rule in their head.<br/><br/>aws&#39;s own comparison: compute SP up to 66% across any family + region + fargate + lambda. ec2 instance SP up to 72% in one family. convertible RI 66% with a manual exchange. standard RI 72% but locked.<br/><br/>at every tier the savings plan matches the rate and beats the flexibility. same rate, less to manage. that&#39;s the whole argument.<br/><br/><a href="https://rajesh.medampudi.com/blog/ri-vs-savings-plans">https://rajesh.medampudi.com/blog/ri-vs-savings-plans</a><br/> <img src="https://media.medampudi.com/2e9d715f05faa8867e3886d26d5502636e537a1f8614f8016fdcc360145b6966.png"> 2026-06-25T17:37:02Z https://nostr.ae/nevent1qqsvt58nn9fdk9xgu0w5y9tgslr0wyrcudzqam6xzl4ujtv2ut35hwczyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukqa4k5v aws nat gateway charges you twice for the same packet. once at $0.045/hr just to exist (~$33/mo per gateway), and again $0.045 for every gigabyte it moves — in and out, on top of normal data transfer.<br/><br/>the hourly fee is visible so nobody worries about it. the per-GB fee is the one that quietly grows, because it rides on traffic you never watch — container pulls, package installs, s3 reads from private subnets.<br/><br/>#aws #infrastructure<br/><br/><a href="https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax">https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax</a><br/> <img src="https://media.medampudi.com/970308496c16bfa0123903f8b0215912ad2b940ef3fd47ff423aafa745b7cde1.png"> 2026-06-25T09:37:02Z https://nostr.ae/nevent1qqsyqsn4ng8xr77sz8jfhxx04xn84dxr57smtkw2pqnj0ev24vd0pwqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukywrv9h lean infrastructure is four decisions, read top to bottom: cut the waste, own past your break-even, observe it cheaply, don&#39;t over-staff.<br/><br/>none of them is a technology. it&#39;s a posture — pay for what genuinely buys you something, refuse to pay for what doesn&#39;t. cut what&#39;s wasted, own what&#39;s worth owning, see everything, staff for the real load. that&#39;s the whole thing.<br/><br/><a href="https://rajesh.medampudi.com/blog/what-lean-infrastructure-means">https://rajesh.medampudi.com/blog/what-lean-infrastructure-means</a><br/> <img src="https://media.medampudi.com/1a2e07b8957c245278e5a1a757c3c4e14394700ce7f610c1f2f5d2922075c781.png"> 2026-06-24T17:37:02Z https://nostr.ae/nevent1qqsxf6a88wxh3yafka2a9kusfm63dyya72hgx7fqynn3xsw2gd3s24szyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukw8svnn at 6 TB of telemetry a day, self-hosted grafana LGTM ran our whole observability platform for ~$15-18K/mo. datadog at the same volume would&#39;ve been ~$120K. that&#39;s 85% less, same telemetry, same scale.<br/><br/>and it gets worse over time — per-GB pricing and compute+storage scale on different curves, so the gap widens as you grow. datadog isn&#39;t a bad tool. you&#39;re just renting a meter that bills you more every time your product succeeds. model your bill at 5x volume before you sign, not after.<br/><br/>#observability #selfhosting #grafana<br/><br/><a href="https://rajesh.medampudi.com/blog/observability-cost-kill">https://rajesh.medampudi.com/blog/observability-cost-kill</a><br/> <img src="https://media.medampudi.com/13aa0856e976f5c57854bb63fab03f047aeda6306d98a569af0abe5f09429c53.png"> 2026-06-24T09:37:02Z https://nostr.ae/nevent1qqsqh3qzxle7m4vwvjd3dykat0dn6rpg0p9teemes3d838cpun8zfrczyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk2c3y7l aws nat gateway charges you twice for the same packet. once at $0.045/hr just to exist (~$33/mo per gateway), and again $0.045 for every gigabyte it moves.<br/><br/>the hourly fee is visible so nobody worries about it. the per-GB fee is the one that quietly grows, because it rides on traffic you never watch — docker pulls, apt installs, s3 reads from private subnets.<br/><br/>open cost explorer, group by usage type, look at NatGateway-Bytes. that&#39;s the number to chase.<br/><br/>#aws #infrastructure #cloudcost #devops 2026-06-22T22:37:02Z https://nostr.ae/nevent1qqs9n7ddz4cfu6v52rr5qrslma8pzsmee2v2zwv9l2puy5cv9wtna0czyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukmah96n at 6 TB of telemetry a day, self-hosted grafana LGTM ran our whole observability platform for ~$15-18K/mo. datadog at the same volume would&#39;ve been ~$120K. an 85% cut.<br/><br/>datadog isn&#39;t a bad tool. the problem is you&#39;re renting something you could own, on a meter that bills you more every time your product succeeds. per-GB pricing is a tax on growth. model your bill at 5x volume before you sign, not after.<br/><br/>#observability #selfhosting #infrastructure 2026-06-22T06:00:01Z https://nostr.ae/nevent1qqstk9juzqkmu8qvddnntac68ac0czeyn6mmrsrq0xy5ukza0ruc2yczyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk98yc3l In reply to <a href='/nevent1qqsz6ppq7wex62gyw5jjc0jdwsq5lesclmxm3d68dyk3fe47hkqkkggpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgm0htah'>nevent1q…htah</a><br/>_________________________<br/><br/>True that. 2026-05-10T11:55:06Z https://nostr.ae/nevent1qqsq6uzz0zf6gnujau7zvwftq4ed22u5587sjyfkafxtzr932h3xy2szyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukj8xqgm <img src="https://media.medampudi.com/38202bd18762f4ac1666f8f7a2426b2d027c103c55b57978e3220c65af43008d.png"> <br/>New blog post: How We Avoided $120K/Month in Observability Costs<br/><br/>Our Datadog bill was $40K/mo and headed to $120K as we scaled. We replaced it with self-hosted Grafana LGTM stack for $15-18K/mo.<br/><br/>The real lesson: per-GB SaaS pricing is a trap at scale. We went from 1TB/day to 6TB/day and our self-hosted costs barely moved. Datadog would have gone from $40K to $120K+.<br/><br/>Self-hosting isn&#39;t just about sovereignty — sometimes the economics leave you no choice.<br/><br/>Full write-up with architecture and timeline:<br/><a href="https://rajesh.medampudi.com/blog/how-we-saved-120k-per-month">https://rajesh.medampudi.com/blog/how-we-saved-120k-per-month</a><br/><br/>#aws #infrastructure #selfhosting #observability #costoptimization<br/><br/> <br/> 2026-04-08T08:26:58Z https://nostr.ae/nevent1qqszlh2gmvm6znrmeln8jfhesl53gnf7zw089rtgyk0zv0hjpaq9jggzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk6p02az In reply to <a href='/nevent1qqsdwclvv3gk7u0wd2f7549jrc3496ctjmmvqn4z2nat6juq57z9a8cpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhglrqreq'>nevent1q…qreq</a><br/>_________________________<br/><br/>So only bitcoin cannot be the strategy and yearly verification and instruction set is the one other step. 2026-04-05T02:21:44Z https://nostr.ae/nevent1qqsgka677wqcaclyp5q9jqekx5x0yajrp27h49hsgjywdla8f3457hczyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk4he8qh My Bitcoin self-custody architecture:<br/><br/>Layer 1: Hardware wallet — keys never touch the internet<br/>Layer 2: 2-of-3 multisig — no single point of failure, geographically distributed<br/>Layer 3: Own node — full verification, no third-party trust<br/><br/>Same engineering principles as infrastructure architecture:<br/><br/>Eliminate single points of failure<br/>Own your data<br/>Verify, don&#39;t trust<br/><br/>After FTX, BlockFi, Celsius — the case for self-custody writes itself.<br/><br/>Not your keys, not your coins.<br/><br/>#bitcoin #selfcustody #sovereignty #nostr<br/><br/><br/> <img src="https://media.medampudi.com/3a525df23ee0c34df6a5848158330daceb1220d2417b3b086144375c12164f5d.png"> 2026-04-04T17:28:28Z https://nostr.ae/nevent1qqswktrryfv0fxt9e3vlaa66wxxtwax8dlpf3wzn4e2wrvynpeq37wqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukj2v8q3 🚨 Just published my first blog post — and it&#39;s about the number that stopped a leadership meeting cold.<br/>We were a gaming company scaling fast. 100K concurrent players. Infrastructure costs climbing 15% month over month. And the biggest line item wasn&#39;t compute or databases — it was observability.<br/>Datadog at 1TB/day: $40K/month. Projecting to 6TB/day: $120K/month.<br/>So we built our own platform for $1,500/month instead.<br/>In the post, I walk through:<br/>→ How tagging AWS resources revealed waste we didn&#39;t know existed<br/>→ Why we replaced Datadog + CloudWatch with a self-hosted LGTM stack (Loki, Grafana, Tempo, Mimir)<br/>→ The surprising architectural change that cut cross-AZ transfer costs and improved reliability<br/>→ What I&#39;d do differently — and the question every engineering team should ask before signing a per-GB vendor contract<br/>If your observability bill is growing with your data volume, you might want to read this before the curve catches up with you.<br/><br/>#AWS #Observability #CostOptimization #Grafana #Datadog #Kubernetes #Engineering<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qvzqqqr4gupzpwc5ww6vzlmfnhqzhlp8efsa2t4k30t70pcynxmvec8cvyjxw27tqqdksmmh94mk2ttnv9mx2epdxyerq6edwpjhyttddah8g6quxrp66" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qv…rp66</a></span> </div> <h1 id="how-we-avoided-120k-month-in-observability-costs-2">How We Avoided $120K/Month in Observability Costs</h1> <p>It was a Tuesday morning leadership meeting. I was looking at the finance slide — the one with the infrastructure cost trendline pointing sharply upward.</p> <p>Our CTO looked at me. As Engineering Manager, the infrastructure decisions rolled up to my team. And I couldn&#39;t explain the number.</p> <p>I knew the bill was growing — everyone did. We were a gaming company scaling fast. A hundred thousand concurrent players on a good day, two hundred thousand on a great one. Infrastructure had to keep up. the technology decisions were mine. But I&#39;d been so focused on keeping the platform alive that I&#39;d never stopped to ask whether we were spending wisely.</p> <p>That question haunted me for the rest of the day. By evening, I&#39;d pulled up AWS Cost Explorer for the first time in months. What I found changed how I think about infrastructure forever.</p> <p><img src="https://media.medampudi.com/814f2938e43a309fe20f8ab75a342934893628cac911759d5d3cbe3475aa4598.png"/></p> <hr> <h2 id="the-number-that-stopped-the-room-2">The Number That Stopped the Room</h2> <p>Our monthly AWS spend was growing 15% month over month. But when I broke it down, the story wasn&#39;t what anyone expected.</p> <p>The biggest cost wasn&#39;t compute. It wasn&#39;t the database. It wasn&#39;t even the hundred thousand concurrent players hammering our game servers.</p> <p>It was <strong>observability</strong>.</p> <p>The observability situation was a mess. We had <strong>three systems running simultaneously</strong> — and none of them gave us the full picture.</p> <p><strong>Datadog</strong> was the &#34;official&#34; monitoring tool. Polished dashboards, easy setup, solid alerting. We were paying <strong>$40,000 a month</strong> for it at 1TB of data per day.</p> <p><strong>CloudWatch</strong> was still running alongside it. Some teams had built dashboards there years ago and never migrated. Others used CloudWatch Logs because that&#39;s where their Lambda functions wrote to by default. Nobody had turned it off. Nobody knew what it cost.</p> <p><strong>SSH and grep.</strong> I wish I was joking. During incidents, engineers were still SSHing into servers and grepping log files. Datadog was supposed to eliminate this, but the search was slow at our volume, results were inconsistent, and old habits die hard. When something was on fire, people reverted to what they trusted: a terminal.</p> <p>Three observability systems. None of them complete. All of them costing money. For a real-time gaming platform with fifty-plus Kubernetes nodes and two hundred services, this wasn&#39;t sustainable.</p> <p>Our data volume was growing fast. Player counts were doubling. Every new feature meant more services, more logs, more metrics, more traces. We were headed toward <strong>6TB/day</strong> within the year.</p> <p>I did the math on a napkin during that leadership meeting. Datadog alone was $40K at 1TB/day — and their pricing scales roughly linearly with volume. At 6TB/day, Datadog alone would be <strong>$120,000 a month or more</strong>. Add CloudWatch costs on top of that — costs nobody was even tracking properly. Plus the hidden cost of engineers wasting time SSHing into servers during incidents because the tools they were paying for weren&#39;t fast enough.</p> <p>More than we&#39;d spend on the game servers themselves.</p> <p>I presented the numbers to the CTO. He gave me the green light to explore alternatives. I had an answer — just not one the finance team would expect.</p> <p><em>&#34;We need to build our own.&#34;</em></p> <p>That&#39;s not a statement you make lightly. Building your own observability platform means owning every outage, every gap in coverage, every 3am page that a SaaS vendor would have handled for you. But the math was undeniable. And I&#39;d rather own the problem at $1,500/month than rent someone else&#39;s solution at $120K.</p> <hr> <h2 id="building-the-replacement-2">Building the Replacement</h2> <p>I became obsessed with the observability problem. Not with cutting costs for the sake of cutting — but with the absurdity of paying $120K/month to read our own logs.</p> <p>Before touching observability though, I needed to understand the full picture. The first thing I did was implement a tagging strategy across every resource in our AWS accounts.</p> <pre><code># Every resource got these tags — no exceptions Tags: Environment: production | staging | development Team: platform | backend | data | infrastructure Service: game-server | matchmaking | analytics | api CostCenter: engineering | operations Owner: team-email@company.com </code></pre> <p>Without tags, Cost Explorer is a wall of numbers. With tags, it becomes a conversation. I could finally answer questions like &#34;how much does matchmaking cost?&#34; and &#34;why is the data team&#39;s spend growing faster than their traffic?&#34;</p> <p>The first week alone revealed something embarrassing: we had seventeen EC2 instances running in staging with average CPU utilization below 5%. Nobody remembered what they were for. Nobody had touched them in months.</p> <hr> <h3 id="the-bet-2">The Bet</h3> <p>With tagging in place, I turned to the real target: that $120K/month observability bill.</p> <p>This was the scariest proposal I&#39;d ever made. You don&#39;t just rip out your monitoring. If something breaks during a tournament with a hundred thousand players online, and you can&#39;t see what&#39;s happening, someone&#39;s getting fired. Probably me.</p> <p>I spent three weeks evaluating alternatives. The answer turned out to be Grafana&#39;s open-source LGTM stack — Loki for logs, Grafana for dashboards, Tempo for traces, Mimir for metrics. All of it running on our own Kubernetes cluster.</p> <p>The architecture was straightforward:</p> <pre><code>Grafana Alloy (collection agent on every node) ↓ Mimir (metrics — Prometheus-compatible, horizontally scalable) Loki (logs — like Prometheus but for log data) Tempo (traces — distributed tracing, S3-backed) ↓ Grafana (visualization, alerting, the UI for everything) ↓ S3 (long-term storage with lifecycle policies) </code></pre> <p>We ran the LGTM stack in parallel with Datadog for a month. Every alert, every dashboard, every on-call query — tested against both. The LGTM stack was faster for log search. The query language (LogQL) was more powerful than anything in Datadog or CloudWatch. The dashboards were more flexible. Engineers stopped SSHing into servers because Grafana actually gave them what they needed in seconds. And we owned the data.</p> <p>The cost comparison told the whole story:</p> <table> <thead> <tr> <th></th> <th>Datadog (projected at 6TB/day)</th> <th>Self-hosted LGTM</th> </tr> </thead> <tbody> <tr> <td>Monthly cost</td> <td>~$120,000</td> <td>~$1,500</td> </tr> <tr> <td>Scales with</td> <td>Data volume (linear)</td> <td>Compute + storage (sub-linear)</td> </tr> <tr> <td>Vendor lock-in</td> <td>Yes</td> <td>No</td> </tr> <tr> <td>Data ownership</td> <td>Theirs</td> <td>Ours</td> </tr> </tbody> </table> <p>At 1TB/day, we were already paying Datadog $40K/month. The LGTM stack handled the same volume for $1,500. But the real win was what happened when we grew to 6TB/day — our costs barely moved. We added some S3 storage, tuned retention policies, and the bill went to maybe $2,000/month. On Datadog, that same growth would have been $120K+.</p> <p>The self-hosted platform was actually <em>better</em>. Unified interface. Custom dashboards. No vendor lock-in. No per-host pricing that punishes you for scaling. Fifteen departments started using it within the first month — because there was no per-seat cost to worry about.</p> <p><img src="https://media.medampudi.com/5b7f66f12361524bbb200c2836cdbf6992ce71e30bcc0f6200155441936763e0.png"/></p> <hr> <h3 id="what-else-we-found-along-the-way-2">What Else We Found Along the Way</h3> <p>The observability deep dive opened our eyes to costs everywhere. Here&#39;s one example that still surprises people: <strong>our multi-AZ architecture was one of our most expensive mistakes.</strong></p> <p>Our EKS cluster was spread across three availability zones. Every best-practice blog post says to do this. High availability. Fault tolerance. Resilience.</p> <p>But nobody mentions the bill.</p> <p>Every time a game server in us-east-1a talked to its Redis cache in us-east-1b, AWS charged us $0.01 per gigabyte. Each direction. Our services were chatty — matchmaking talked to the player database, game servers talked to the session cache, analytics talked to everything. At our traffic levels, cross-AZ data transfer was costing thousands every month.</p> <p>The fix was counterintuitive: we moved to a <strong>cell-based architecture</strong>. Instead of spreading each service across all three AZs, we created self-contained cells. Each cell ran in a single AZ. Game servers, their caches, their databases — all co-located. HA came from having multiple cells, not from spreading one service thin.</p> <pre><code># Karpenter provisioner for a single-zone cell apiVersion: karpenter.sh/v1alpha5 kind: Provisioner metadata: name: cell-us-east-1a spec: requirements: - key: topology.kubernetes.io/zone operator: In values: [&#34;us-east-1a&#34;] - key: karpenter.sh/capacity-type operator: In values: [&#34;spot&#34;, &#34;on-demand&#34;] consolidation: enabled: true </code></pre> <p>Pod-to-pod latency dropped from 1-2ms (cross-AZ) to under 0.5ms (same AZ). Node utilization went from 20% to 65% because Karpenter could consolidate efficiently within each cell. Cross-AZ transfer costs nearly disappeared.</p> <p>And here&#39;s the part that surprised the whole team: <strong>reliability improved</strong>. When a cell had an issue, it was isolated. Other cells kept running. The blast radius of any single failure shrank dramatically.</p> <p><img src="https://media.medampudi.com/41eee5ae5dc90fc1d560e1574b95b958968d0231636eeabd9c3ba170bbcd209d.png"/></p> <hr> <h3 id="the-quiet-wins-2">The Quiet Wins</h3> <p>The observability project cracked open the door to everything else. Once we had proper tagging and visibility, obvious savings appeared everywhere — S3 lifecycle policies cut storage costs by 96%, free VPC endpoints eliminated NAT Gateway charges, and Reserved Instances on databases we&#39;d been running On-Demand for two years saved another $8K/month.</p> <p>None of these are clever. They&#39;re obvious — once you look. I&#39;ll write about each of them separately.</p> <hr> <h2 id="the-timeline-2">The Timeline</h2> <p>The observability migration took about six weeks from evaluation to full cutover. The parallel-run period was the longest part — we needed absolute confidence before decommissioning CloudWatch.</p> <table> <thead> <tr> <th>Week</th> <th>What We Did</th> </tr> </thead> <tbody> <tr> <td>1-2</td> <td>Evaluated LGTM stack, built proof of concept on staging</td> </tr> <tr> <td>3</td> <td>Deployed to production alongside CloudWatch (parallel run)</td> </tr> <tr> <td>4</td> <td>Migrated dashboards, alerts, and on-call queries</td> </tr> <tr> <td>5</td> <td>Onboarded all 15 departments to Grafana</td> </tr> <tr> <td>6</td> <td>Decommissioned CloudWatch, cancelled Datadog evaluation</td> </tr> </tbody> </table> <p><strong>Result: We replaced Datadog ($40K/month), decommissioned CloudWatch, and eliminated the need to grep server logs — all with a single $1,500/month self-hosted platform. And avoided what would have been $120K+/month in Datadog alone as our data grew to 6TB/day.</strong></p> <p>Three fragmented systems became one. The LGTM stack scaled with us. Datadog&#39;s pricing would have scaled against us.</p> <p>Once the observability win was in, the momentum made everything else easier. Leadership stopped questioning infrastructure costs and started asking what we could optimize next. Over the following months, we found significant savings across compute, storage, and networking — but those are stories for another post.</p> <hr> <h2 id="what-i-d-do-differently-2">What I&#39;d Do Differently</h2> <p>If I could go back, I&#39;d change two things.</p> <p><strong>I&#39;d build the LGTM stack earlier.</strong> We ran CloudWatch and LGTM in parallel for a month out of caution. In hindsight, two weeks would have been enough. The self-hosted stack was clearly better within days. That extra two weeks of parallel running cost us $40K we didn&#39;t need to spend.</p> <p><strong>I&#39;d question the pricing model earlier, not just the price.</strong> When Datadog was at $40K/month, it felt manageable. The problem wasn&#39;t the current bill — it was the trajectory. I should have modeled the cost at 2x, 5x, 10x our data volume before we ever signed the contract. Per-GB pricing on a platform that generates more data every quarter is a trap. The question isn&#39;t &#34;can we afford this today?&#34; — it&#39;s &#34;can we afford this at scale?&#34;</p> <hr> <h2 id="the-real-lesson-2">The Real Lesson</h2> <p>That Tuesday morning finance slide was the best thing that happened to our infrastructure. Not because of the $120K/month in savings — though that&#39;s hard to argue with. But because it exposed a blind spot every engineering team has.</p> <p>We&#39;d been running CloudWatch on autopilot for two years. Debug logs with infinite retention. Custom metrics nobody queried. Dashboards nobody opened. The bill grew 15% month over month and nobody questioned it, because nobody connected &#34;what we&#39;re logging&#34; with &#34;what we&#39;re paying.&#34;</p> <p>The observability vendor market depends on this blindness. They price per host, per GB ingested, per million events — units that scale linearly with your infrastructure. The more you grow, the more you pay. It&#39;s a tax on success. And the tax rate gets worse, not better, at scale.</p> <p>Self-hosted observability inverts this. Your costs are the compute to run the stack and the S3 storage underneath it. Both scale sub-linearly with data volume. We went from 1TB/day to 6TB/day and our observability bill went from $1,500 to about $2,000. On Datadog, that same growth would have taken us from $40K to $120K+.</p> <p>Every company I&#39;ve talked to since has the same trajectory. They&#39;re at 1TB now, growing fast, and their vendor bill is growing faster. By the time the CFO notices, they&#39;re locked in.</p> <p>So here&#39;s my question: what&#39;s your observability costing you today, and what will it cost at 5x your current volume? Not the sticker price — the projected cost. The curve, not the point.</p> <p>You might not like what you find. But you&#39;ll be glad you looked before the bill arrived.</p> <hr> <p><em>I write about infrastructure, observability, and the decisions behind the systems. Follow me on <a href="https://njump.me/npub1hv288dxp0a5emsptlsnu5cw496mgh4l8suzfndkvuruxzfr8909sdqkqdn">Nostr</a> or find me at rajesh.medampudi.com.</em></p> <p><em>Zap me: rajesh@medampudi.com</em></p> </blockquote> 2026-03-30T12:14:49Z https://nostr.ae/nevent1qqs9w5lumf9gketmhwlzrhefhkdpdxnwg9cw0g3aljjmhhtlm8hk2cszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk0mzp2x Hey Nostr 👋<br/><br/>I&#39;m Rajesh — platform engineer, 17+ years building distributed systems.<br/><br/>What I&#39;ve built:<br/>• Observability platforms processing 6TB/day at 85% below SaaS costs<br/>• Saved $120K/month on AWS for a gaming platform with 100K+ concurrent players<br/>• Infrastructure serving 100K+ concurrent users in real-time<br/><br/>What I&#39;ll post here:<br/>• Technical deep dives (AWS, K8s, observability, self-hosting)<br/>• Building in public — shipping, breaking, learning<br/>• Bitcoin &amp; sovereignty — running my own node, relay, and media server<br/>• Long-form articles via kind:30023<br/><br/>I run my own Nostr relay (nostr.onbitcoinstandard.com), Blossom media server (media.medampudi.com), and my blog pulls content directly from Nostr at build time.<br/><br/>The protocol is the platform.<br/><br/>⚡ rajesh@medampudi.com<br/>🌐 rajesh.medampudi.com<br/><br/> <img src="https://media.medampudi.com/0ae64cd73183238ee034f75e35faf2b1e00cd2865cd8492384b24012ce9cc0eb.png"> 2026-03-30T09:52:20Z https://nostr.ae/nevent1qqszkmxkh0wvju4wm5jpfr6d72lvncehh26408a599wkjl43ehpuzlgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukujl5q9 Hey Nostr 👋<br/><br/>I&#39;m Rajesh — platform engineer, 17+ years building distributed systems.<br/><br/>What I do:<br/>• Built observability platforms processing 6TB/day at 85% below SaaS costs<br/>• Saved $120K/month on AWS for a gaming platform with 100K+ concurrent players<br/>• Building Simbotix — bringing enterprise-grade infra to small businesses<br/><br/>What I&#39;ll post here:<br/>• Technical deep dives (AWS, K8s, observability, self-hosting)<br/>• Building in public — shipping, breaking, learning<br/>• Bitcoin &amp; sovereignty — running my own node, relay, and media server<br/>• Long-form articles via kind:30023<br/><br/>My stack: I run my own Nostr relay (nostr.onbitcoinstandard.com), Blossom media server (media.medampudi.com), and my blog pulls content directly from Nostr at build time.<br/><br/>The protocol is the platform.<br/><br/>⚡ rajesh@medampudi.com<br/>🌐 rajesh.medampudi.com 2026-03-30T08:15:16Z https://nostr.ae/nevent1qqspygg4ct69ktteu04ra6ud8w4u3jm849gc2xuhr2304rw00tfgekgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uklaeqe8 write test 1774858422814 2026-03-30T08:13:42Z https://nostr.ae/nevent1qqsp80ku76hspyc3043q8ezqqy3ftyteca24w3gu8xyzenxpryjd04qzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk4mt3mg relay write test - Rajesh 2026-03-30T08:05:27Z https://nostr.ae/nevent1qqsqgmy4v5y3c8qqmlvxsea23qeqr7pwvka9e6wgsxxyvyekt88w74czyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukwdyfvj Hey Nostr 👋<br/><br/>I&#39;m Rajesh — platform engineer, 17+ years building distributed systems.<br/><br/>What I do:<br/>• Built observability platforms processing 6TB/day at 85% below SaaS costs<br/>• Saved $120K/month on AWS for a gaming platform with 100K+ concurrent players<br/>• Building Simbotix — bringing enterprise-grade infra to small businesses<br/><br/>What I&#39;ll post here:<br/>• Technical deep dives (AWS, K8s, observability, self-hosting)<br/>• Building in public — shipping, breaking, learning<br/>• Bitcoin &amp; sovereignty — running my own node, relay, and media server<br/>• Long-form articles via kind:30023<br/><br/>My stack: I run my own Nostr relay (nostr.onbitcoinstandard.com), Blossom media server (media.medampudi.com), and my blog pulls content directly from Nostr at build time.<br/><br/>The protocol is the platform.<br/><br/>⚡ rajesh@medampudi.com<br/>🌐 rajesh.medampudi.com 2026-03-30T08:01:04Z https://nostr.ae/nevent1qqsrn70unnkn6sxrzp30838sq46jpk6qapd3sgg8wurwu423nevu2ugzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukfylh0e In reply to <a href='/nevent1qqsp4mq2sydtjks3ec04henw8dy6ct50ccld0d33hfkd0yc4lnjy8fcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsdxdc7f'>nevent1q…dc7f</a><br/>_________________________<br/><br/>seems like you have not touched yakihonne.... tell me what is so better in AMETHYST that is not there in yakihonne. 2025-08-23T16:51:21Z https://nostr.ae/nevent1qqs8uesp2dvjm8pgtu95n4dxrm5gtalumrf97kf8nv590e9c7guw5ggzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk848sth In reply to <a href='/nevent1qqsr9zwwqcz6f9t4ayk3g4r5dkndagtawxyke8lvz88yfa7dp9qx6pg8ynx8q'>nevent1q…nx8q</a><br/>_________________________<br/><br/>Then you realised you are not driving at all, just sitting beside the driver. 2025-01-31T20:48:49Z https://nostr.ae/nevent1qqsfw5yg6txupg42tnn2cd84lk3hld35qf3jd72sar04wjp4999tjfgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukru9p6t In reply to <a href='/nevent1qqswl0hqz0jt0jgnj4feeq3synm72avwfmmmjgctsc7dmqrajamt5egjnlaxe'>nevent1q…laxe</a><br/>_________________________<br/><br/>Bitcoin comes to you only when you are ready that could be at <br/>$1, <br/>$10, <br/>$100, <br/>$1000, <br/>$10000, <br/>$100000, <br/>$1000000. <br/><br/>Where did you get into it 🤔 2024-12-14T17:22:19Z https://nostr.ae/nevent1qqsg5vjpkwf36euwf8rdsqau8xu4kjn6mcyfz3j7janyhd0fl0fr4zqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk8e79v9 In reply to <a href='/naddr1qqrryv3kxs6nxq3qxhe6ymx3ua6669k6mrxgar5afqjeljxtgc3shjtx8jqj0yka7gcsxpqqqp65w0c27m7'>naddr1qq…27m7</a><br/>_________________________<br/><br/>Build your own seed signer, you don&#39;t need to buy anything from them. No secure element for seed signer for sure. The rest all are addressed with it. 2024-12-02T10:31:20Z https://nostr.ae/nevent1qqs85hahpmf4s4kg64rw4m4rptnz2yqhm6mhx5a4n2aq6ru0k5a2fxszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk668tzv In reply to <a href='/nevent1qqsg2jehjfwat4pngmv8x6g63ktmxtnhhrse4ketfqfhakygva6m9xg6q5n7z'>nevent1q…5n7z</a><br/>_________________________<br/><br/>1bitcoin is 100million sats, What happens after sats. Things are definitely going to cost us 0.00001 sat in the future 2024-11-26T03:24:21Z https://nostr.ae/nevent1qqsp3v5fy99vm8pnd7yxx20qa9pumdrat09nwgnq7nexyty2rxx2nxgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk97v8zg In reply to <a href='/nevent1qqsyxaumaluc8lrpjkwk7jpsq3v67lnpr37c5qwx5u787ygekgc4f5c7axzsz'>nevent1q…xzsz</a><br/>_________________________<br/><br/>Good keep it up. Which path are you taking. Dev or cloud associte. 2024-11-20T14:55:04Z https://nostr.ae/nevent1qqs2hqnxc6q6tx35cz76c30ypyxmue00g60ahh3698z6fnqz6q90nxgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukxs0hjr In reply to <a href='/nevent1qqstkh5fqvvgvmc9rm55rae9uy78ekw4jwrjwma9vvnmg8r29phxtkqydjpng'>nevent1q…jpng</a><br/>_________________________<br/><br/>There are many linux versions oriented for windows users. 2024-11-16T03:58:06Z https://nostr.ae/nevent1qqsycvhyxngp8a4mhqg4ajcx9a65vugfsq64xtnyuk209qlr7f3ytsszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukf8s46d <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub103m96sra82w4agghew9cdxtzs4s8sl7qsjsvw6h653yml0gjrkzqefd3h5" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Jor</span> (<span class="italic">npub103m…d3h5</span>)</a></span> you got to give this a try. It changed my life on nostr<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/note1kd27wzj8ejfhncjperhdg2s7p58cvkfvv82mvs429mc5rk2gajdqd8kqws" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">note1kd2…kqws</a></span> </div> Announcing YakiHonne 2.0: Simpler, Faster, and Built for Creators! This version brings two main improvements:<br/><br/>1. Complete Redesign:<br/> • Onboarding: Easily create a non-custodial wallet with Npub & Nsec, experience zapping (Lightning payments), or browse as a guest.<br/> • Home & Discover: “Discover” is designed for creators, focusing on rich formats like long-form content, videos, and curated works. “Home” offers a social feed with short notes and curated contents, making it quick and easy for creators to share their work.<br/> • Wallet: Simple setup with easy creation, direct YakiHonne node linking, and multi-wallet support.<br/> • Dashboard: Manage all published and drafted content, check stats, and pick up right where you left off—all in one place.<br/> • Notifications: Reactions, Reposts, Mentions, Zaps, Comments, and Follows now appear in clear, categorized cards.<br/> • Settings: Completely revamped for simplicity, now including profile customization, appearance, relay settings, and wallet management.<br/><br/>2. Enhanced Performance:<br/>Our re-engineered core now supports the outbox model with extensive functionality. Furthermore, Thanks to PabloF7z we now have seamless data fetching, caching, and full support of the NDK implementation.<br/><br/>Hope you enjoy the new decentralized media experience! 🌐✨Try it out here::<br/> •Web: yakihonne.com<br/> •App Store (iOS): <a href="https://apps.apple.com/us/app/yakihonne/id6472556189">https://apps.apple.com/us/app/yakihonne/id6472556189</a><br/> •Google Play (Android): <a href="https://play.google.com/store/apps/details?id=com.yakihonne.yakihonne&hl=en">https://play.google.com/store/apps/details?id=com.yakihonne.yakihonne&hl=en</a><br/><br/>Thank you for your incredible support on this decentralized media journey!<br/><br/><video controls width="100%" class="max-h-[90vh] bg-neutral-300 dark:bg-zinc-700"><source src="https://v.nostr.build/Uu1uXf8P5D9KkBw6.mp4"></video><br/> </blockquote> 2024-11-13T21:59:40Z https://nostr.ae/nevent1qqsv2wef769cfv540awp5f0uql9zwpftn3gkfjjwczaypkn0aeh9hxgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk3kn2rn In reply to <a href='/naddr1qqxnzdenxy6r2d3exycnvv3cqgsywh3wstzzwhf3phz4jvcey9xpfyrammg6y6ml2s2kphecqftm5hcrqsqqqa28dn28fx'>naddr1qq…28fx</a><br/>_________________________<br/><br/>Unable to zap you???? 2024-11-13T21:57:46Z https://nostr.ae/nevent1qqs2a7jk9ufxpnu0md045ftjmy9epjmy0s66z9m9v00w9kpsr53kp4qzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukdzj6tl Tru that<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/note1gjdtfxhyfspkrrnheeynvnragrpkav0y25zmttxld3wk7kwe90csprhnzw" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">note1gjd…hnzw</a></span> </div> Lesson from this year: lawyers like telling you what you can’t do, not what you can<br/><br/>Offer you want to build, just do it </blockquote> 2024-11-13T21:34:38Z https://nostr.ae/nevent1qqsfy8kgkhymqpnktdqwjqc5g9m66acqx4stek20cagzqqgu366vr5qzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukrr0x2y In reply to <a href='/nevent1qqsfm429n8zhtav6xzly6f9urm86xckeltc0ncd4mnhvmeaeg5frjdqmegjjz'>nevent1q…gjjz</a><br/>_________________________<br/><br/> <img src="https://media4.giphy.com/media/QAsHga1AB6dIGUsui6/200w.webp?cid=4ea4f8d5fmgfm9caxxsqe3f0ccf7zwauwlppe77j2ptv33sx&amp;ep=v1_gifs_search&amp;rid=200w.webp&amp;ct=g"> 2024-11-13T21:33:17Z https://nostr.ae/nevent1qqsdr6mx4uvfes7s23ymyfhup07c7f5rxdyd6aa07pnkuy6l3cy7spqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukdn6yex In reply to <a href='/nevent1qqstr45ddf8mvuuuun6msslm66qn487uk77zv80yduqfjcccq0frcds06z5zy'>nevent1q…z5zy</a><br/>_________________________<br/><br/>Hnd gloves 2024-11-13T21:30:55Z https://nostr.ae/nevent1qqsdxgeare8f26mm6ladg7ryxaq0z2ugej39sjnvgmqqxagnxu5kvngzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uknrcule In reply to <a href='/nevent1qqsxkyfhtgwg9j2cyz9samksvn2tgu8nrhjgg0ql2ngtnrcg9zngpjsqnjxaz'>nevent1q…jxaz</a><br/>_________________________<br/><br/>And I sell at $66k, it still hurts. But seeing my credit card at zero is something delightful. 2024-11-13T21:26:34Z https://nostr.ae/nevent1qqsx5ehf4vvellz94jj3krwxuam6asdnvtt93484pp50kf624su3zwgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukd8p00e In reply to <a href='/nevent1qqsd0f7fv24zpvxmjm0ldgvj5gkn6ywmhc3qwz797jvg73v03kt0dvsjqh6jm'>nevent1q…h6jm</a><br/>_________________________<br/><br/>Let the central paper bitcoin gobble up the money until they cannot. And then the low tide comes where we see who is swimming butt naked. 2024-11-13T21:19:41Z https://nostr.ae/nevent1qqsd9s3ynyzc0wtrndx3yhcfungh2zryjnrt2v5v6jmj2aedh8vsktczyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukj7grp7 In reply to <a href='/nevent1qqsvphzszuwfvdyqzg88z3ylv87lavxed0qpdqsp32yg45cw4xgua7cmgxc6m'>nevent1q…xc6m</a><br/>_________________________<br/><br/>Jor I think you need to come up with a numeric system In emojis so that we can count from here on. <br/><br/>The people who follow you know or can dig deep down the rabbit hole for the mapping. 2024-11-13T17:06:47Z https://nostr.ae/nevent1qqspnp7lmxvyy548dj9p89dlc7rqq6fu5e0xwmxjkzyfxr5sqdlsr9gzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukuanct3 In reply to <a href='/nevent1qqsqhwpfyhjg8flvxl659xqe4lclkgpf0nemz62ktk6fcmzpvrwtuusjpjaa2'>nevent1q…jaa2</a><br/>_________________________<br/><br/>Them coming to nostr is a sure fire way to make them right. Because providing value is what nostr values and earns. And propogates. No status quo. 2024-11-09T16:39:51Z https://nostr.ae/nevent1qqs9d5p4v0t44d3jal6jz5d785836r3ftqjzqgh993m7sxtgxsgwvkgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukxwgfw2 In reply to <a href='/nevent1qqs27573q86klc7m9vrsww2v9gfsxy2n5lp5n44klzqp7s62e6v9lnqx4kdys'>nevent1q…kdys</a><br/>_________________________<br/><br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Alby</span> (<span class="italic">npub1get…0nfm</span>)</a></span> kudos to your service. Love it so simple to use. 2024-11-08T17:46:01Z https://nostr.ae/nevent1qqsq4fnj9a0499dn5ldts4ec7kcpceapttvevg7xuajfjc3gtj5fpqqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukeqlzdj In reply to <a href='/nevent1qqspxhdc75ne9ywf7fefrla7nxp0qece2e4uqh2k9me3lpl8k3j0czgknvugm'>nevent1q…vugm</a><br/>_________________________<br/><br/>I cannot comment about that last statement. She might come back or be in picture for the next time. 2024-11-06T18:40:46Z https://nostr.ae/nevent1qqsg8k8h2x7yg3pslwyfe69f4927j9muwfv4u7yrh8hlspcevwd0zcgzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukq45dnp In reply to <a href='/nevent1qqsxljq22cv36gz22sy9vawrmt8a4scuacmn2cshgt8lp47f4nmzussg908f2'>nevent1q…08f2</a><br/>_________________________<br/><br/>Loving the community. 2024-11-06T12:25:11Z https://nostr.ae/nevent1qqsfw0eqhankfec4dvkd3udne3c67chtlfg0lk4ntvpqefqx9wj8n8gzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukcppzaa In reply to <a href='/nevent1qqswtsdw37t3v7nxjyutvpgtjc5gep2w8j6cnq9xs25v3ypzydx30nslyaf2g'>nevent1q…af2g</a><br/>_________________________<br/><br/>😁 2024-11-06T04:06:45Z https://nostr.ae/nevent1qqs0sxv29ucqcy8c7ld8qgmku5tjls2sgh2x5gm8sq9hlhfe7q0p7rqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukarw8yz In reply to <a href='/nevent1qqspyknkaswd6dxysyhchx0ycse8a9dmcnhx580uj3u0cvqw7a4ckgskptk24'>nevent1q…tk24</a><br/>_________________________<br/><br/>Hindu so no to steak. Would love some lamb or chichen though. 2024-11-05T20:39:57Z https://nostr.ae/nevent1qqs98pplqaazh85825cgntf43jtq74f75q90n08jvmp8e3f842tva8szyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukyqxlnh In reply to <a href='/nevent1qqsymes9jhqh48gzvjx06k37cue6sg065dnwj6fuac63lnehdfd7pegdsv6tm'>nevent1q…v6tm</a><br/>_________________________<br/><br/>It is like any other crypto out there. Valuable to the eyes of the beholder only. But if you are comparing it with replacing btc nope. None. 2024-11-05T20:34:01Z https://nostr.ae/nevent1qqsw6v5xruj8z7r7vqku2nt2ev883mduglaf9j5pdnczt4qfe2edusqzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukg8dxcw In reply to <a href='/nevent1qqszruvfwk9jcamk9tt4de39v5ctd59w283kwysda3dztcfr7xaw3qgqz8lfa'>nevent1q…8lfa</a><br/>_________________________<br/><br/>Good show today jor. Thanks for the crazy knowledge you impart. 2024-11-05T20:31:48Z https://nostr.ae/nevent1qqstmca5fqkngsfpdenjmmfcjkwk7mwljdgr44c7xq37ecewwut5c0szyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukd80u2a In reply to <a href='/nevent1qqsgu0kpmn6qxdlheyrrgq93k6v346vrl7ax6r35q05pncp7kjkvarstzj323'>nevent1q…j323</a><br/>_________________________<br/><br/>True that. 2024-11-04T20:35:45Z https://nostr.ae/nevent1qqs86kevjr2ryqcs7du926y696nt7vqkuandjwll8v4kkkr6e9225aszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukan8gx5 In reply to <a href='/nevent1qqsf6jzz8weekppnxwpqg42eu33g0de40snx4ayqzhzc9k0txwdlxxspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs5c8k8s'>nevent1q…8k8s</a><br/>_________________________<br/><br/>Remember, remember, the Fifth of November, <br/>The Gunpowder Treason and Plot. <br/>I see of no reason <br/>Why the Gunpowder Treason<br/>Should ever be forgot... 2024-11-04T19:22:43Z https://nostr.ae/nevent1qqsy80t0g43znhw6kzd4f5dkga7yxljrk5yc49vevl08w9jmjkqsufszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukday7r8 In reply to <a href='/nevent1qqsf6jzz8weekppnxwpqg42eu33g0de40snx4ayqzhzc9k0txwdlxxspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs5c8k8s'>nevent1q…8k8s</a><br/>_________________________<br/><br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub103m96sra82w4agghew9cdxtzs4s8sl7qsjsvw6h653yml0gjrkzqefd3h5" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Jor</span> (<span class="italic">npub103m…d3h5</span>)</a></span> Tomorrow is the day. <br/> 2024-11-04T19:00:43Z https://nostr.ae/nevent1qqsf6jzz8weekppnxwpqg42eu33g0de40snx4ayqzhzc9k0txwdlxxszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukxphpq0 V Fro Vendetta - Remember remember the 5th of November. <br/><br/><video controls width="100%" class="max-h-[90vh] bg-neutral-300 dark:bg-zinc-700"><source src="https://video.nostr.build/dafe2d01f2ad68850ffebd6a0add58c48197b3544a19ad7b5b3014019beb66a7.mp4"></video> 2024-11-04T18:53:08Z https://nostr.ae/nevent1qqspwrxq9kyph5mkgz42yeyjasvyuxzmee6hsjqjkjlsttxmmqamdnszyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4uk3uana8 Bitcoin as designed. <br/><br/><a href="https://bitcoin.org/bitcoin.pdf">https://bitcoin.org/bitcoin.pdf</a> 2024-10-19T13:22:57Z https://nostr.ae/nevent1qqsfttl3r2juu5j74nnxum0g3t584qca7536sr8ww0hpxgmes64vz3qzyza3gua5c9lkn8wq907z0jnp65htdz7hu7rsfxdkens0scfyvu4ukrd09j0 Crypto != Bitcoin 2024-10-17T17:25:35Z