Bastion Project

Open source

Become a contributor

Financial contributions

Custom contribution

Donation

Make a custom one time or recurring contribution.
Recurring contribution

backer

Become a backer for $5.00 per month and help us sustain our activities!

Starts at

$5 USD / month

2 individuals have contributed

Recurring contribution

supporter

Join us for $15.00 per month and help us sustain our activities!

Starts at

$15 USD / month

Recurring contribution

sponsor

Become a sponsor for $100.00 per month and help us sustain our activities!

Starts at

$100 USD / month

Top financial contributors

1
Robin Mattheussen

$45 USD since Dec 2019

2
Shane Sveller

$20 USD since Jul 2020

Budget

See how money openly circulates through Bastion Project. All contributions and all expenses are published in our transparent public ledger. Learn who is donating, how much, where is that money going, submit expenses, get reimbursed and more!

Monthly financial contribution to Bastion Project (backer)

from Shane Sveller9/1/2020

+$10.00USD
Completed

Monthly financial contribution to Bastion Project (backer)

from Robin Mattheussen9/1/2020

+$5.00USD
Completed

Monthly financial contribution to Bastion Project (backer)

from Robin Mattheussen8/1/2020

+$5.00USD
Completed

Today’s balance

$52.82 USD

Estimated annual budget

~ $148.92 USD

Bastion Project is all of us

Our contributors 3

Everyone who has supported Bastion Project. Individuals and organizations that believe in –and take ownership of– our purpose.

Robin Mattheu...
Financial Contributor

Total contributions

$45 USD

backer

Shane Sveller
Financial Contributor

Total contributions

$20 USD

backer

About

What is Bastion?

Bastion is a fault-tolerant runtime which is designed for recovering from faults based on the supervision strategies that you've passed. It is designed to provide persistent runtime for applications which need to be highly-available.

Why Bastion?

If one of the questions below answered with yes, then Bastion is just for you:

  • Do I need fault-tolerancy in my project?
  • Do I hate to implement weird Actor traits?
  • I shouldn't need a webserver to run an actor system, right?
  • Do I want to make my existing code unbreakable?
  • Do I have some trust issues against orchestration systems? Because I want to implement my own application lifecycle.

Features

  • Message-based communication makes this project a lean mesh of actor system.
  • without web servers, weird shenanigans, forced trait implementations, and static dispatch.
  • Runtime fault-tolerance makes it a good candidate for small scale distributed system code.
  • If you want to smell of Erlang and it's powerful aspects in Rust. That's it!
  • Supervision makes it easy to manage lifecycles.
  • Kill your application in certain condition or restart you subprocesses whenever a certain condition met. All up to you. And it should be up to you.