#process-manager #process #manager #daemon #cli #daemonize #nodejs

app kurv

A process manager to daemonize commands and programs. Inspired by pm2, but lightweight and not as featureful.

2 releases

0.0.2 Jan 4, 2024
0.0.1 Jan 4, 2024

#192 in Command line utilities

MIT license

2.5K SLoC

๐ค๐ฎ๐ซ๐ฏ is a process manager, mainly for Node.js and Python applications. It's written in Rust. It daemonizes your apps so that they can run in the background. It also restarts them if they crash.

Crates.io Version

Docs โ€ข Crate โ€ข Readme

Heads up, this project is my Rust-learning playground and not production-ready yet:

  • I built this because my apps needed a process manager, and I had an itch to learn Rust. So, here it is... my first Rust project!
  • No tests yet (oops!)
  • Tested only on Windows 11
  • Rust newbie alert! ๐Ÿšจ
  • Using it for my own projects, but not on a grand scale

Why ๐ค๐ฎ๐ซ๐ฏ?

So, why the name ๐ค๐ฎ๐ซ๐ฏ? Well, it means "basket" in many languages I don't speak, like Norwegian (but it sounded cool ๐Ÿ˜„). Think of ๐ค๐ฎ๐ซ๐ฏ as a basket for your apps. In kurv, we call each deployed app as an egg. So, let's go and collect some eggs ๐Ÿฅš in your basket ๐Ÿงบ.


[!NOTE] ๐ค๐ฎ๐ซ๐ฏ can run either as a server or as a CLI client, using the same binary.

The server is responsible for managing the eggs, while the client is used to interact with the server and tell it what to do or ask it for information.

Download binaries

Download the latest release from GitHub.


You can also install it from crates.io using cargo:

cargo install kurv


kurv usage

Start the server

To get the server rolling, type:

kurv server


  • ๐ค๐ฎ๐ซ๐ฏ will create a file called .kurv where it will store the current state of the server. The file will be created in the same directory where the binary is located or in the path specified by the KURV_HOME_KEY environment variable.

  • since ๐ค๐ฎ๐ซ๐ฏ can be used both as a server and as a client, if you want to run it as a server, you need to set the KURV_SERVER environment to true. This is just a safety measure to prevent you from running the server when you actually want to run the client. To bypass this, you can use the --force flag (kurv server --force)

Collect some ๐Ÿฅš

To deploy/start/daemonize an app (collect an egg), do:

kurv collect <egg-cfg-path>

The path should point to a YAML file that contains the configuration for the egg.

It should look something like this:

name: fastapi # the name of the egg / should be unique
command: poetry # the command/program to run
args: # the arguments to pass to the command
  - run
  - serve
cwd: /home/user/my-fastapi-app # the working directory in which the command will be run
env: # the environment variables to pass to the command

This will run the command poetry run serve in /home/user/my-fastapi-app with the environment variable FASTAPI_PORT set to 8080.

If for some reason, the command/program crashes or exits, ๐ค๐ฎ๐ซ๐ฏ will revive it!

Show me my eggs

If you want a summary of the current state of your eggs, run:

$ kurv list

๐Ÿฅš eggs snapshot

โ”‚ # โ”‚ pid   โ”‚ name      โ”‚ status  โ”‚ โ†บ โ”‚ uptime โ”‚
โ”‚ 1 โ”‚ 35824 โ”‚ fastapi   โ”‚ running โ”‚ 0 โ”‚   1s   โ”‚
โ”‚ 2 โ”‚ 0     โ”‚ fastapi-2 โ”‚ stopped โ”‚ 0 โ”‚   -    โ”‚

For details on a specific egg:

$ kurv egg <egg:name|id|pid>

This will show you the egg's configuration, process details, etc.

Stop an egg

To halt an egg without removing it:

$ kurv stop <egg:name|id|pid>

This will stop the process but keep its configuration in the basket in case you want to start it again later.

Remove an egg

To actually remove an egg, run:

$ kurv remove <egg:name|id|pid>

It will stop the process and remove the egg from the basket.


If you need the process to be restarted, run:

$ kurv restart <egg:name|id|pid>



Inspired by the robust process manager, pm2, my goal with ๐ค๐ฎ๐ซ๐ฏ was to create a lightweight alternative. Not that pm2 is a resource hog, but I found myself in a server with extremely limited resources. Plus, I was itching for an excuse to dive into Rust, and voila, ๐ค๐ฎ๐ซ๐ฏ was born.


Derived from eggsecutor, ๐ค๐ฎ๐ซ๐ฏ adopted the whimsical term "eggs" to represent deployed applications.


Insights from pueue were instrumental in helping me understand how to manage processes in Rust.

With ๐Ÿง‰ from Argentina ๐Ÿ‡ฆ๐Ÿ‡ท


~221K SLoC