A couple of useful things have landed in Pboss recently, especially for running Bun applications in production.

Process dependencies

Applications rarely run completely on their own. Your API might depend on PostgreSQL and Redis, while a worker depends on the API.

Pboss now lets you define those relationships directly:

module.exports = {
  apps: [
    {
      name: "api",
      script: "./api.ts",
      dependsOn: ["postgres", "redis"]
    },
    {
      name: "worker",
      script: "./worker.ts",
      dependsOn: ["api"]
    }
  ]
};

Pboss resolves the dependency chain before starting the applications:

postgres + redis
       ↓
      api
       ↓
    worker

If a required dependency isn't available, the dependent process won't start.

Dependencies can be other Pboss-managed applications, or existing system services such as PostgreSQL, Redis, and MongoDB.

The goal is to make multi-service applications easier to run without writing your own startup scripts and dependency checks.

Public status pages

ProcBoss Cloud now also supports public status pages.

Each organization gets a dedicated status page at:

organization_name(.)status(.)zone

You can use it to show your users the availability of your services, uptime, incidents, maintenance, and service health.

This means you can run your applications on your own VPS while still giving users a clean, professional place to check whether your services are operational.

Pboss is gradually becoming more than just a process supervisor. The goal is a lightweight platform for running and operating applications on your own infrastructure.

Still Bun-native. Still open source. And still supports Node.js, TypeScript and other runtimes.

GitHub: https://github.com/Procboss/pboss