Hacker News: ajayvk

New comment by ajayvk in "Htmx 4.0"

ajayvk — Sat, 29 Aug 2026 02:55:44 +0000

Go backend with Starlark for dynamic behavior is a great combination. I have been building https://github.com/openrundev/openrun 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 https://utils.demo.clace.io/console/

New comment by ajayvk in "Automatic Litestream Replication for any SQLite app"

ajayvk — Wed, 26 Aug 2026 18:37:14 +0000

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.

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.

Automatic Litestream Replication for any SQLite app

ajayvk — Wed, 26 Aug 2026 18:37:14 +0000

Article URL: https://openrun.dev/blog/litestream/

Comments URL: https://news.ycombinator.com/item?id=49453745

Points: 2

# Comments: 1

New comment by ajayvk in "Lovable raises $400M Series C"

ajayvk — Thu, 13 Aug 2026 01:14:36 +0000

Custom agents can be added if it supports ACP, the console UI has the config options for that.

I have tested with GitHub and GitLab. OpenRun uses the go-git library, so BitBucket should work, not tried it yet.

FastHTML is great for internal tools use case.

New comment by ajayvk in "Lovable raises $400M Series C"

ajayvk — Thu, 13 Aug 2026 00:20:24 +0000

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.

New comment by ajayvk in "Lovable raises $400M Series C"

ajayvk — Wed, 12 Aug 2026 22:35:16 +0000

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.

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 https://github.com/openrundev/openrun/issues?q=is%3Aissue%20...

New comment by ajayvk in "Lovable raises $400M Series C"

ajayvk — Wed, 12 Aug 2026 21:54:18 +0000

There is too much friction in deploying internal tools. I have been building https://github.com/openrundev/openrun to solve that. Full GitOps (create/update your app through GitOps, not just updating app source code), staged deployments, service bindings (for getting a managed database credential, instead of creating a new database per app) and OIDC/SAML with RBAC.

New comment by ajayvk in "What job interviews taught me about Kubernetes"

ajayvk — Tue, 16 Jun 2026 03:26:46 +0000

Targeting a specific use case (internal tools) should hopefully help avoid feature creep. Also, the goal is that an OpenRun config should work on a single-node with Docker and with Kubernetes. That limits the types of features which can be implemented (for example no Docker Compose support, no Helm support).

New comment by ajayvk in "What job interviews taught me about Kubernetes"

ajayvk — Tue, 16 Jun 2026 01:20:59 +0000

I don't think you can provide all the features of Kubernetes while reducing the complexity. What is possible is to support a subset of the features of Kubernetes while making it easy to use.

https://github.com/openrundev/openrun is a project I am building. It supports declarative deployments, on a single-node with Docker or onto Kubernetes. The target use cases is limited to standalone web app, like internal tools. No support for stateful services, you manage stateful services yourself. With that simplification, OpenRun provides a much easier developer experience.

New comment by ajayvk in "Ask HN: What are you working on? (June 2026)"

ajayvk — Sun, 14 Jun 2026 16:38:27 +0000

Been working on making it much easier for application deployments to get access to a isolated database/schema. The usual pattern currently is to assume that each app creates a new database, which ignores the backups, monitoring etc required for each database. Implemented support for Postgres and MySQL.

Wrote up more details at https://openrun.dev/blog/service-binding/

New comment by ajayvk in "Service Binding – Easy database access for apps"

ajayvk — Sun, 14 Jun 2026 15:53:00 +0000

I have been building the OpenRun https://github.com/openrundev/openrun project over the last three years. Recently added support for Postgres and MySQL service bindings. After you configure the admin credentials for your database service, any new app can just ask for a binding and get a unique schema/database. Backups, monitoring, capacity planning etc can be done once for the main database, instead of repeating it for every new app.

Service Binding – Easy database access for apps

ajayvk — Sun, 14 Jun 2026 15:49:38 +0000

Article URL: https://openrun.dev/blog/service-binding/

Comments URL: https://news.ycombinator.com/item?id=48528556

Points: 2

# Comments: 1

New comment by ajayvk in "Service Bindings for Postgres: Per-App Roles and Grants"

ajayvk — Fri, 12 Jun 2026 19:37:15 +0000

Service binding is a feature that only large systems like Cloud Foundry support till now. Even Kubernetes does not have a functional implementation, the Red Hat operator is deprecated. It is a very useful feature, it allows you to configure a Postgres/MySQL service once and then each new app can easily bind and get a unique schema/database within the main database instance. Much simpler than the alternative of managing a separate database service for each app or sharing a service by either using same credentials or manually provisioning unique credentials.

I have been building the OpenRun https://github.com/openrundev/openrun project over the last three years. Recently added support for Postgres and MySQL service bindings. The flow is configure the admin credentials for your database service. After that, any new app can just ask for a binding and get a unique schema/database. Backups, monitoring, capacity planning etc can be done once for the main database, instead of repeating it for every new app.

Service Bindings for Postgres: Per-App Roles and Grants

ajayvk — Fri, 12 Jun 2026 19:17:17 +0000

Article URL: https://openrun.dev/blog/service-binding/

Comments URL: https://news.ycombinator.com/item?id=48508307

Points: 3

# Comments: 1

Blocking Copy Fail (CVE-2026-31431) in Kubernetes with Tetragon

ajayvk — Sun, 03 May 2026 00:11:18 +0000

Article URL: https://isala.me/blog/mitigating-copy-fail-with-tetragon/

Comments URL: https://news.ycombinator.com/item?id=47991862

Points: 1

# Comments: 0

New comment by ajayvk in "I am building a cloud"

ajayvk — Fri, 24 Apr 2026 00:27:58 +0000

Kubernetes offers powerful low-level primitives that can support virtually any deployment architecture. However, working with these primitives directly requires significant YAML wrangling. It makes sense to build specialized solutions on top of Kubernetes that simplify common deployment patterns. Knative is one such solution. Any solution that tries to expose all underlying primitives will inevitably become as complex as Kubernetes itself.

I have been building https://github.com/openrundev/openrun, which provides a declarative solution to deploy internal web apps for teams (with SAML/OAuth and RBAC). OpenRun runs on a single-machine with Docker or it can deploy apps to Kubernetes.

New comment by ajayvk in "Microsoft offers buyouts up to 7% of US employees"

ajayvk — Thu, 23 Apr 2026 21:15:28 +0000

Makes no sense if you look at the start menu as an interface to the operating system.

Makes perfect sense if you look at it as one more place to show ads

GitHub's Fake Star Economy

ajayvk — Tue, 14 Apr 2026 19:22:35 +0000

Article URL: https://awesomeagents.ai/news/github-fake-stars-investigation/

Comments URL: https://news.ycombinator.com/item?id=47770182

Points: 4

# Comments: 3

New comment by ajayvk in "Ask HN: What Are You Working On? (March 2026)"

ajayvk — Mon, 09 Mar 2026 01:21:18 +0000

Have been building a project https://github.com/openrundev/openrun/ which aims to make it easy for teams to easily deploy internal tools/webapps. While creating new apps has gotten easier, securely deploying them across teams remains a challenge. OpenRun runs as a proxy which adds SAML/OAuth based auth with RBAC. OpenRun deploys containerized apps to a single machine with Docker or onto Kubernetes.

Currently adding support for exposing Postgres schemas for each app to use. The goal is that with a shared Postgres instance, each app should be able to either get a dedicated schema or get limited/full access to another app's schema, with row level security rules being supported.

New comment by ajayvk in "Migrating from Heroku to Magic Containers"

ajayvk — Sat, 07 Mar 2026 16:49:10 +0000

Cloud Run makes lots of sense when running lots of small apps, apps scale to zero automatically.

I have been building https://github.com/openrundev/openrun which provides similar scale down to zero functionality, on a single machine with Docker or on top of Kubernetes.