<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: ajayvk</title><link>https://news.ycombinator.com/user?id=ajayvk</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 19 Nov 2026 22:47:20 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=ajayvk" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by ajayvk in "Show HN: OpenRun v1.0 – declarative deploys for internal tools on Docker or K8s"]]></title><description><![CDATA[
<p>I have been building OpenRun as a part-time project over the last three years. The project has few companies using it in production. I am happy to announce a 1.0 release.<p>OpenRun makes declarative deployments easy, on a single machine with Docker/Podman or on Kubernetes. It is built for teams to deploy internal tools. So it has features like OIDC/SAML based auth with RBAC for restricting access to apps, service bindings for access to isolated databases and scaling idle apps down to zero.</p>
]]></description><pubDate>Tue, 17 Nov 2026 18:27:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=50535914</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=50535914</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50535914</guid></item><item><title><![CDATA[Show HN: OpenRun v1.0 – declarative deploys for internal tools on Docker or K8s]]></title><description><![CDATA[
<p>Article URL: <a href="https://openrun.dev/blog/openrun-1.0/">https://openrun.dev/blog/openrun-1.0/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=50535810">https://news.ycombinator.com/item?id=50535810</a></p>
<p>Points: 1</p>
<p># Comments: 1</p>
]]></description><pubDate>Tue, 17 Nov 2026 18:20:36 +0000</pubDate><link>https://openrun.dev/blog/openrun-1.0/</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=50535810</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50535810</guid></item><item><title><![CDATA[Code-First Internal Tools vs. Low-Code in the Age of AI]]></title><description><![CDATA[
<p>Article URL: <a href="https://openrun.dev/blog/code-first-internal-tools/">https://openrun.dev/blog/code-first-internal-tools/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=50347878">https://news.ycombinator.com/item?id=50347878</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 03 Nov 2026 03:59:46 +0000</pubDate><link>https://openrun.dev/blog/code-first-internal-tools/</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=50347878</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50347878</guid></item><item><title><![CDATA[New comment by ajayvk in "Sites in ChatGPT"]]></title><description><![CDATA[
<p>I have been building <a href="https://github.com/openrundev/openrun" rel="nofollow">https://github.com/openrundev/openrun</a>. OpenRun allows you to build web apps, adding OIDC/SAML with RBAC to control who can access the apps. Supports MCP for app management. Also supports service bindings, which enables providing each app an isolated database account.</p>
]]></description><pubDate>Fri, 02 Oct 2026 19:38:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=49937651</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49937651</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49937651</guid></item><item><title><![CDATA[New comment by ajayvk in "Cloud in a Bottle: making self-hosting accessible to everyone"]]></title><description><![CDATA[
<p>I have been building <a href="https://github.com/openrundev/openrun" rel="nofollow">https://github.com/openrundev/openrun</a> which makes auth (OIDC/SAML) with RBAC easy for self-hosted apps.</p>
]]></description><pubDate>Sun, 06 Sep 2026 20:52:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=49590821</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49590821</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49590821</guid></item><item><title><![CDATA[New comment by ajayvk in "Show HN: Cowbull – Wordle-like game where you only get match counts"]]></title><description><![CDATA[
<p>Great. The multi-player mode is also fun, that is what I play the most. You can create a challenge and send the link to friends or family. They can join and it keeps track of the leaderboard. Every player gets the same sequence of words.<p>I just made this 3 word challenge <a href="https://cowbull.co/challenge/6TQZ" rel="nofollow">https://cowbull.co/challenge/6TQZ</a>, try it</p>
]]></description><pubDate>Sun, 06 Sep 2026 02:39:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=49582787</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49582787</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49582787</guid></item><item><title><![CDATA[Show HN: Cowbull – Wordle-like game where you only get match counts]]></title><description><![CDATA[
<p>CowBull is a word game where you have to find the hidden four-letter word. You make guesses and get back the count of exact letter matches (bulls) and partial matches (cows). It’s a bit like Wordle, but you are not told the exact letters which match, only the count of matching letters.<p>Scoring is based on the number of guesses and time used. There is a single player mode and a multi-player mode (no account required). The game source code is at <a href="https://github.com/claceio/cowbull" rel="nofollow">https://github.com/claceio/cowbull</a>.<p>When I was younger, we used to play this game on paper at the back of the classroom during school and college in India. During Covid, I made this online version of the game to play with my kids.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49582216">https://news.ycombinator.com/item?id=49582216</a></p>
<p>Points: 4</p>
<p># Comments: 2</p>
]]></description><pubDate>Sun, 06 Sep 2026 00:37:31 +0000</pubDate><link>https://cowbull.co/</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49582216</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49582216</guid></item><item><title><![CDATA[New comment by ajayvk in "Running SQLite Apps on Docker and Kubernetes with Litestream"]]></title><description><![CDATA[
<p>That comment was about what happens during an app deployment, to avoid multiple pods on Kubernetes from writing to the same volume. Multiple apps on one OpenRun have no issues, the replication will be identify them as different.<p>If by mistake you actually have two separate instances of OpenRun pointing to the same S3 volume and path_prefix (with single-node Docker or with Kubernetes), the generated S3 paths have an binding ID which should be unique across instances. I will check whether there is anything more which can be done to prevent any issues with such an incorrect config.</p>
]]></description><pubDate>Sun, 30 Aug 2026 20:35:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=49502495</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49502495</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49502495</guid></item><item><title><![CDATA[New comment by ajayvk in "Running SQLite Apps on Docker and Kubernetes with Litestream"]]></title><description><![CDATA[
<p>Not a company :-) OpenRun has been a passion project I have been building for last three years, trying to make declarative deployments easier</p>
]]></description><pubDate>Sun, 30 Aug 2026 19:43:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=49502065</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49502065</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49502065</guid></item><item><title><![CDATA[New comment by ajayvk in "Running SQLite Apps on Docker and Kubernetes with Litestream"]]></title><description><![CDATA[
<p>On Kubernetes, for apps using SQLite, maxReplicas is set to 1 and OpenRun uses the Recreate update strategy. This ensures at most one pod is active (requests are queued until the new pod is healthy). There should never be more than one pod accessing the SQLite database.</p>
]]></description><pubDate>Sun, 30 Aug 2026 19:39:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=49502025</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49502025</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49502025</guid></item><item><title><![CDATA[New comment by ajayvk in "Running SQLite Apps on Docker and Kubernetes with Litestream"]]></title><description><![CDATA[
<p>Without persistent volumes, every deployment of the app may require the SQLite data to be restored from S3, which can take time if database size is large. With PVC, regular app deployments use existing database, only a disaster recovery scenario restores from S3.<p>Yes, it feels magical to just recreate your namespace or even create a new K8s cluster and see all your apps (from OpenRun metadata) and app data restored automatically.</p>
]]></description><pubDate>Sun, 30 Aug 2026 19:09:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=49501795</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49501795</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49501795</guid></item><item><title><![CDATA[New comment by ajayvk in "Running SQLite Apps on Docker and Kubernetes with Litestream"]]></title><description><![CDATA[
<p>Built-in Litestream replication and automatic restore is a new feature I added in OpenRun (a self-hosted deployment platform for web apps). Apps can use SQLite with zero code changes while OpenRun handles backup/recovery. This works on a single node with Docker/Podman and also on Kubernetes.</p>
]]></description><pubDate>Sun, 30 Aug 2026 18:08:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=49501182</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49501182</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49501182</guid></item><item><title><![CDATA[Running SQLite Apps on Docker and Kubernetes with Litestream]]></title><description><![CDATA[
<p>Article URL: <a href="https://openrun.dev/blog/litestream/">https://openrun.dev/blog/litestream/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49501147">https://news.ycombinator.com/item?id=49501147</a></p>
<p>Points: 30</p>
<p># Comments: 14</p>
]]></description><pubDate>Sun, 30 Aug 2026 18:05:06 +0000</pubDate><link>https://openrun.dev/blog/litestream/</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49501147</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49501147</guid></item><item><title><![CDATA[New comment by ajayvk in "Htmx 4.0"]]></title><description><![CDATA[
<p>Yes, OpenRun can deploy any containerized application and act like a proxy for the  upstream application, no Starlark or any transformation in OpenRun. If the upstream container is serving JSON APIs, OpenRun can also be used to implement a Hypermedia based web app on top, using Go HTML templates and Starlark as the glue code.<p>The advantage is that you get the performance of Go while being able to hot reload applications and install new application dynamically without a process restart. I think of it as an application server for containerized applications.</p>
]]></description><pubDate>Sat, 29 Aug 2026 17:11:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=49491522</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49491522</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49491522</guid></item><item><title><![CDATA[New comment by ajayvk in "Htmx 4.0"]]></title><description><![CDATA[
<p>Go backend with Starlark for dynamic behavior is a great combination. I have been building <a href="https://github.com/openrundev/openrun" rel="nofollow">https://github.com/openrundev/openrun</a> with that approach, mainly for teams to deploy internal tools. It can be used to deploy any containerized application. The management UI for OpenRun is built with the Hypermedia approach <a href="https://utils.demo.clace.io/console/" rel="nofollow">https://utils.demo.clace.io/console/</a></p>
]]></description><pubDate>Sat, 29 Aug 2026 02:55:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=49486478</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49486478</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49486478</guid></item><item><title><![CDATA[New comment by ajayvk in "Automatic Litestream Replication for any SQLite app"]]></title><description><![CDATA[
<p>I’ve been working on making SQLite a first-class production option in OpenRun. OpenRun is a self-hosted deployment platform for web apps and internal tools which I have been building as a side project for last three years. Built-in Litestream replication and automatic restore is a new feature I added, so apps can use SQLite while OpenRun handles backup/recovery. This works on a single node with Docker/Podman and also on Kubernetes.<p>You define the S3 config once on the server, and every SQLite app gets continuous replication and automatic restore using Litestream. The app image stays unchanged. The server's own metadata is replicated too, through Litestream embedded as a Go library.</p>
]]></description><pubDate>Wed, 26 Aug 2026 18:37:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=49453746</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49453746</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49453746</guid></item><item><title><![CDATA[Automatic Litestream Replication for any SQLite app]]></title><description><![CDATA[
<p>Article URL: <a href="https://openrun.dev/blog/litestream/">https://openrun.dev/blog/litestream/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49453745">https://news.ycombinator.com/item?id=49453745</a></p>
<p>Points: 2</p>
<p># Comments: 1</p>
]]></description><pubDate>Wed, 26 Aug 2026 18:37:14 +0000</pubDate><link>https://openrun.dev/blog/litestream/</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49453745</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49453745</guid></item><item><title><![CDATA[New comment by ajayvk in "Lovable raises $400M Series C"]]></title><description><![CDATA[
<p>Custom agents can be added if it supports ACP, the console UI has the config options for that.<p>I have tested with GitHub and GitLab. OpenRun uses the go-git library, so BitBucket should work, not tried it yet.<p>FastHTML is great for internal tools use case.</p>
]]></description><pubDate>Thu, 13 Aug 2026 01:14:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=49280702</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49280702</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49280702</guid></item><item><title><![CDATA[New comment by ajayvk in "Lovable raises $400M Series C"]]></title><description><![CDATA[
<p>The agent based app builder is pretty new, still improving it. It runs with Agent Client Protocol (ACP), with integrations for Claude Code, Codex CLI, OpenCode and Pi.</p>
]]></description><pubDate>Thu, 13 Aug 2026 00:20:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=49280314</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49280314</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49280314</guid></item><item><title><![CDATA[New comment by ajayvk in "Lovable raises $400M Series C"]]></title><description><![CDATA[
<p>OpenRun runs on a single machine, with either Docker or Podman. All apps runs on that one machine. Idle apps are scaled down to zero, so resource usage is low even when hundreds of apps are installed. For scaling up, OpenRun can be deployed on Kubernetes.  Each app deployed through OpenRun gets created as a Kubernetes deployment, again with scaling down to zero. Same declarative config moves from singe node to Kubernetes, no changes required.<p>I don't have any telemetry, so not sure about number of users. Based on issues filed, lots of users using the single node deployment (which is good enough for most use cases). Started with Streamlit/Gradio type apps, now users are actually using it for deploying vibe coded internal tools. See <a href="https://github.com/openrundev/openrun/issues?q=is%3Aissue%20state%3Aclosed" rel="nofollow">https://github.com/openrundev/openrun/issues?q=is%3Aissue%20...</a></p>
]]></description><pubDate>Wed, 12 Aug 2026 22:35:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=49279509</link><dc:creator>ajayvk</dc:creator><comments>https://news.ycombinator.com/item?id=49279509</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49279509</guid></item></channel></rss>