<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Nami Smart LLC Blog</title><description>Work and writing from Nami Smart LLC. From adding languages and search visibility to a cross-border shop, to consolidating club tools into a multi-tenant SaaS, we cover planning through to running it in production.</description><link>https://namismart.net/</link><language>en</language><item><title>Starting this blog: what Nami Smart LLC does</title><link>https://namismart.net/en/blog/hello-namismart/</link><guid isPermaLink="true">https://namismart.net/en/blog/hello-namismart/</guid><description>We have opened the Nami Smart LLC engineering blog. Here is what we build, and the technical decisions we care about.</description><pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate><category>Announcements</category><category>About us</category></item><item><title>Why we wrote an ORM only for Cloudflare D1</title><link>https://namismart.net/en/blog/why-we-built-d1zzle/</link><guid isPermaLink="true">https://namismart.net/en/blog/why-we-built-d1zzle/</guid><description>Why a general-purpose ORM does not shrink under tree-shaking, and how rebuilding it for D1 alone cut the minified bundle by 43%.</description><pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate><category>Cloudflare</category><category>D1</category><category>TypeScript</category><category>Open source</category></item><item><title>A Cloudflare stack that runs a cross-border shop with no fixed costs</title><link>https://namismart.net/en/blog/zero-fixed-cost-cloudflare-stack/</link><guid isPermaLink="true">https://namismart.net/en/blog/zero-fixed-cost-cloudflare-stack/</guid><description>How to run an online shop for a worldwide audience without a monthly server bill, and how the work is divided between Astro, Workers, D1, R2 and Stripe.</description><pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate><category>Cloudflare</category><category>Astro</category><category>E-commerce</category><category>Architecture</category></item><item><title>Putting all of our infrastructure in code, rather than catching up to what was built by hand</title><link>https://namismart.net/en/blog/infra-as-code-pulumi-sops/</link><guid isPermaLink="true">https://namismart.net/en/blog/infra-as-code-pulumi-sops/</guid><description>How we brought the infrastructure of several products into one repository with Pulumi, SOPS and GitHub Actions, including the steps we left manual and why.</description><pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate><category>Pulumi</category><category>IaC</category><category>Cloudflare</category><category>Security</category></item></channel></rss>