capataz: OTP-like supervision trees in Haskell

[ concurrency, control, library, mit ] [ Propose Tags ]

capataz enhances the reliability of your concurrent applications by offering supervision of green threads that run in your application.

Advantages over standard library:

  • Links related long-living processes together under a common capataz supervisor, with restart/shutdown order

  • Set restart strategies (Permanent, Transient, Temporary) on IO sub-routines on a granular level

  • Set restart strategies on a pool of long-living worker threads (AllForOne, OneForOne)

  • Complete telemetry on the sub-routine lifecycle of your application (start, error, restarts, shutdown)

[Skip to Readme]


Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


  • No Candidates
Versions [RSS],,,,,,
Change log
Dependencies async (>= && <2.3), base (>=4 && <5), bytestring (>=0.10.8), pretty-show (>=1.6.13), prettyprinter (>=1.1), rio (>=, teardown (>=, time (>=1.6.0), uuid (>=1.3) [details]
License MIT
Copyright © 2018, 2019 Roman Gonzalez and Collaborators
Author Roman Gonzalez
Category Control, Concurrency
Home page
Bug tracker
Source repo head: git clone
Uploaded by RomanGonzalez at 2019-05-21T02:29:57Z
Reverse Dependencies 1 direct, 0 indirect [details]
Downloads 4055 total (12 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2019-05-21 [all 1 reports]

Readme for capataz-

[back to package description]


Our greatest glory is not in never failing, but in rising every time we fail.– Confucius

Table Of Contents


Hackage Stackage LTS Stackage Nightly

Make sure you include the following entry on your cabal file's dependecies section.

  build-depends: capataz

Or on your package.yaml

- capataz


The documentation website can be found here. Some relevant links:


Build Status Github Hackage Dependencies

Follow the developer guidelines

In future releases

  • Replace Protolude in favor of RIO
  • Documentation of performance analysis
  • Ensure unit tests always finish on all concurrent scenarios (dejafu experiment)