This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Documentation

This is where the Amybo documentation lives - lets keep all the learning available and usefully organised here. If you’re new you may want to start of with the:

Overview

Other content such as discussions, trial results, case studies, and community updates should live in the Community pages.


1 - Overview

How we hope to democratise food.

What is Amybo?

Amybo is a diverse community of people interested in unlocking the secrets of protein fermentation. Our aim is that anyone will be able to produce tasty, nutritious protein at a lower financial cost and much lower environmental cost than by raising animals to eat.

What are we doing now?

Initially, we have quite a list of questions to answer:

  1. Which protein should we ferment first?
  2. What equipment will we need to ferment it?
  3. How should we share our results to best accelerate open source development?
  4. How can we ensure that the products we make are safe to eat?

You are invited to join us in creating pages on this site addressing these issues (and any other’s we haven’t yet thought of)

Join Us

1.1 - Next steps

Plan of campaign

Next steps

  1. Pick a protein producing microbe to cultivate
  2. Pick a bioreactor to cultivate it with
  3. Conduct initial risk assessment (each subsequent step will start with a risk assesment)
  4. Design/build/procure the bioreactor
  5. Dry commission the bioreactor
  6. Wet commission the bioreactor
  7. Live commision the bioreactor
  8. Cultivate the protein producing microbe
  9. Determine next steps required to produce safe nutricious delicious protein

2 - Microbes

What microbes should we cultivate?

Step one in protein development is deciding which protein to develop first. Choice of bioreactor, feedstocks and downstream processing are all dependent on the organisms we use and the proteins they produce. This page is very much a work in progress and your input would be hugely welcome.

A note on “closed source” enterprises

We mention a number of commercial “closed source” companies below. We fully support their efforts to bring the benefits of alternative proteins. Commercial competition has brought many excellent innovations to market. Many companies seek to do good, even before seeking profit, however there is a risk that good companies and/or their IP gets acquired by less benevolent enterprises. Shareholder primacy means that some of the world’s poorest, in the most challenging environments may not benefit as much as they could from the innovations that they need most. Open source projects like this serve to benefit all corporations (as they can access our data) while also ensuring our innovations have the potential to benefit all.

Our Protein Shortlist

Algal protein

Through photosynthesis, algae use sunlight to produce sugar and oxygen from carbon dioxide and water. Nitrogen can be metabolised from urea, meaning all major feedstocks are freely available.

As such (and since a number of algae, containing all essential amino acids, are already sold as ‘superfoods’ for human consumption) algal protein may be the quickest win. That said, it may not be as gastronomically appealing as other proteins on our shortlist.

Arthrospira platensis

Spirulina is commonly used as a food supplement, but Spirulina Gnocchi has been proposed by the European Space Agency for Mars Missions. It has a slightly sweet nutty taste. Spirulina is technically a cyanobateria rather than algae, which means the risk of cyanotoxins (e.g. microcystin, alkaloids and BMAA) need to be mitigated.

Chlorella

Chlorella arguably tastes worse than Spirulina. They also have a lower protein concentration and cellulose walls. In their favour: they are single celled, so may be easier to process, and should not produce cyanotoxins.

Biomass fermentation

Biomass fermentation is where the whole microbe (or a dried version) is the product.

Given the relative ease of downstream processing when the whole microbe is used, and their gastronomic potential, biomass fermentation may be the preferred route for open source fermentation.

Fusarium venenatum

Quorn mycoprotein is a well known proprietary product of biomass fermentation. It uses Fusarium venenatum, a filamentous fungi. Quorn’s original patents expired in 2010 but their £30M fermentation towers may prove challenging for open source development.

Sustainable Bioproducts, Inc and 3F Bio Ltd have also submitted Fusarium venenatum GRAS (Generally Recognised As Safe) notices to the US-FDA.

Harrison Lab have published bioinformatic analysis of Fusarium venenatum genomes on GitHub.

Cupriavidus necator

Solar Foods use Cupriavidus necator to produce their proprietary Solein largely from air. They take carbon dioxide and water vapour from air. They use solar powered hydrolysis to split the water, providing hydrogen which C. necator can use as its energy source. Ammonia is used as the nitrogen source.

Novo-Nutrients and Kiverdi are also thought to use Cupriavidus necator.

Precision fermentation

Precision fermentation is where microbes are used to produce particular chemicals. Insulin and rennet are common cited products of precision fermentation. Fooditive are one company using Precision fermentation to produce casein - the main protein in milk, cheese, yoghurt and similar dairy products.

The separation processes required to extract the end products of precision fermentation will likely make it a more complex process than biomass fermentation. As such we anticipate that the proteins will be more expensive to make and harder to democratise.

Precision fermentation also frequently involves genetic engineering. We anticipate that corporations who invest in the development of custom strains for precision fermentation may be less inclined to open source them.

Other Types of Protein

Cultivated Meat

The Good Food Institute and New Harvest have useful primers on cultivated meat. This may play an important role in mimicking and replacing traditional meat. However, the complexity and cost of doing so, without any significant nutritional benefits over our protein shortlist candidates, mean that it may be best left to well-funded enterprises.

Plant Based Meat

Tofu and Tempeh are examples of ancient meat alternatives. Beanburgers and veggie burgers took the next step in vegetarian fast food. More recently companies like Beyond Meat and Impossible Foods have taken great strides in meat alternatives.

We are also inclined to leave plant based meat to well-funded enterprises, as they generally offer no nutritional benefits over the plants they are made from, and naturally requires plants, which have their own downsides - see below.

Tempeh is an Indonesian fermented soybean protein source that is definitely worth trying. Domingo Club have developed an open source Tempeh fermenter for those of us who live in colder climates than Indonesia.

Meat & Plant Protein

Plants are definitely a more sustainable source of protein than highly inefficient traditional meat. Only a fraction of the protein that livestock eats makes its way into the meat that we eat.

Plant-based protein production still requires significantly more land, and in many cases more water, carbon emissions, fertilisers, pesticides, herbicides, etc. than any of our protein shortlist candidates. Given the inefficiencies of current agribusiness cultivation, this results in significant discharge of nutrients and other environmentally detrimental chemicals into water courses.

There are many improvements that can be made to crop cultivation. For example The Land Institute are doing wonderful work on perennial crops. Many small (and not-so-small) scale farmers and horticulturalists are doing wonderful things around both increasing yields and decreasing environmental impact.

Climate change poses an existential threat, it is essential that we reduce GHG emissions from food production and all other activities. Even if we manage this we still need to adapt to climate change. There are already populated places on earth where natural crop cultivation is impossible. Microbial protein production could be sustainable in all such regions. Our challenge is to ensure that it is economically viable and available to all who need it.


3 - Equipment

Which equipment should we use?

Commercial competition is an established means of driving innovation. However, as with the microbes and processes, development of either open source or generic equipment may be necessary to ensure that those who most need them can afford them.

Using an open source equipment also enables you to both customise it’s capabilities, and contribute to it’s development.

General purpose lab ware should be relatively easy to procure, and toxicity and chemical analysis can initially be outsourced to commercial labs. There are some more expensive pieces of equipment to focus on:


3.1 - Bioreactors

Which bioreactors should we use?

Once you have determined which protein you wish to cultivate, the next question is what you are going to cultivate it in. There is a need for development of better and more efficient bioreactors across the board - but, given the nature of this project, it makes sense to, at least initially, restrict our scope to open source bioreactors.

Bioreactor Shortlist

Pioreactor

“The Pioreactor is an open-source, affordable, and extensible bioreactor platform.

It currently comes in a cute and cost-effective 20 ml version that can be used in batch, fed batch, continuous, chemostat, turbidostat & PID morbidostat modes. While the software is already open source, we understand from the founder that the hardware and 3D designs are due to be made open source in 2023.

Exciting features for Amybo (as of June 2023):

  • it appears to be more affordable than most automated bioreactors
  • it will soon be fully open source, hence customisable
  • it is clearly under active development
  • it is available for sale with excellent lead times
  • you can add LEDs as a light source for algae
  • the system is compatible with DormantBioLabResources’ open source modular lab racks

Wish list (as of June 2023):

  1. Ability to automatically upload results to a project cloud database
  2. larger vessels - so probes can be added
  3. Easy-open viewport cover (it currently requires 4 screws)
  4. 3D printer files - to minimise shipping cost & carbon, and enable community development
  5. Ability to control temperature below ambient
  6. Ability to wall-mount for bioreactor farms & video production
  7. Fully assembled units (including pre-configured raspberry pi’s) for technophobes
  8. Global stockists - to reduce shipping time, cost and carbon
  9. A way to be certain that reactor overflow isn’t going to fry your raspberry pi

Other Open Source Bioreactors

Hackuarium’s bioreactor

Watch also Open source bioreactor

Concerns (as of June 2023):

  1. last commit was 7 months ago
  2. It doesn’t appear to be commercially available although full assembly instructions and a detailed bill of materials are given

Phenobottle

Watch Photobioreactor (Phenobottle)

Concerns (as of June 2023):

  1. last commit was 2 years ago

EVE-Pi

See also biorxiv article

Concerns (as of June 2023):

  1. last commit was 2 years ago

New Harvest Open Source Bioreactor

See also IRNAS

Concerns (as of June 2023):

  1. last commit was 3 years ago

Biomaker Open Source Bioreactor Project

See also Biomakespace and Hackster

Concerns (as of June 2023):

  1. last commit was 5 years ago.
  2. chat channel is a dead link

3.2 - Autoclaves

Which sterilisation systems should we use?

Open Source Autoclave Shortlist

This is a short list, there are a number of open source autoclave control projects:

But the only open source project that claims to deliver a full autoclave, is in our opinion just a thermal steriliser, as it doesn’t appear to pressurise the sterilisation volume.

It may well be that open source autoclaves are too risky. The probability of an explosion with an incorrectly constructed unit is high and the consequences could be lethal.

Given the high risk and low volumes of sales a commercial autoclave would likely be the most expensive item on our equipment list. So we should consider pressure cookers:

Pressure cookers

Electronic

Metallic Black GPC201SS-20 5.5L 1000W Pressure Cooker

Exciting features for Amybo (as of June 2023):

  • Low price
  • Can be used outside the kitchen (no hob required)

Concerns (as of June 2023):

  • Can it accurately monitor and control temperature and pressure?
  • Will condensation be an issue? (Autoclaves use dry steam)

Stovetop

Ikea 365+

Prestige

Other Open Source “Autoclaves”

OpenAutoclave

See also Open Autoclave: Build an open-source off-grid medical instrument sterilizer, Open Source Medical Autoclave for Developing World, Open Autoclave: a Humanitarian Maker Project

Concerns (as of June 2023):

  1. How can this maintain pressure, and if it doesn’t, how can it be called an autoclave?

3.3 - Microscopes

Which microscopes should we use?

Microscopes are third on the list of major open source equipment, because it is very possible to conduct fermentation without a microscope. It would however be much more difficult and less rewarding if you could never see your microbes. Microscopy also plays a valuable role in detecting contamination by unwanted microbes.

Fortunately there are a good number of open source microscopy projects:

Our Microscope Shortlist

Open Flexure

See also:

UC2

See also A versatile and customizable low-cost 3D-printed open standard for microscopic imaging

openFrame

PUMA

See also A Research Grade Open Source Microscope — Made with FreeCAD

Other Open Source Microscopes


4 - Contribution Guidelines

How to contribute to the Amybo community

Reach out to us

Please add a comment to one of our YouTube videos or drop us a line at hello@amybo.org with any suggestions or questions you may have - or just to say hello, it’s good to know people are reading this.

If you’re comfortable with GitHub (or would like to learn) we’d absolutely love it if you were happy to dive in and edit our pages directly:

Editing Amybo.org

We welcome contributions and improvements to the Amybo.org website. We want this to be as easy as possible so considered a wiki. However, given the controversial nature and risks associated with protein production for human consumption, we decided that an approvals process was required.

Since we’ll be using GitHub for software development at least, and potentially also for hardware and procedure development, it made sense to use this for community development of the website. If you struggle at all with GitHub development, please get in touch via hello@amybo.org

Web stack

We use Hugo to format and generate our website, the Docsy theme for styling and site structure, and Netlify to manage the deployment of the site. Hugo is an open-source static site generator that provides us with templates, content organisation in a standard directory structure, and a website generation engine. You write the pages in Markdown (or HTML if you want), and Hugo wraps them up into a website.

All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult GitHub Help for more information on using pull requests.

Quick start

Here’s a quick guide to updating the docs. It assumes you’re familiar with the GitHub workflow and you’re happy to use the automated preview of your doc updates:

  1. Fork the Amybo pages repo on GitHub.
  2. Make your changes and send a pull request (PR).
  3. If you’re not yet ready for a review, add “WIP” to the PR name to indicate it’s a work in progress. (Don’t add the Hugo property “draft = true” to the page front matter, because that prevents the auto-deployment of the content preview described in the next point.)
  4. Wait for the automated PR workflow to do some checks. When it’s ready, you should see a comment like this: deploy/netlify — Deploy preview ready!
  5. Click Details to the right of “Deploy preview ready” to see a preview of your updates.
  6. Continue updating your doc and pushing your changes until you’re happy with the content.
  7. When you’re ready for a review, add a comment to the PR, and remove any “WIP” markers.

Updating a single page

If you’ve just spotted something you’d like to change while using the docs, Docsy has a shortcut for you:

  1. Click Edit this page in the top right hand corner of the page.
  2. If you don’t already have an up to date fork of the project repo, you are prompted to get one - click Fork this repository and propose changes or Update your Fork to get an up to date version of the project to edit. The appropriate page in your fork is displayed in edit mode.
  3. Follow the rest of the Quick start process above to make, preview, and propose your changes.

Previewing your changes locally

If you want to run your own local Hugo server to preview your changes as you work:

  1. Follow the instructions in Getting started to install Hugo and any other tools you need. You’ll need at least Hugo version 0.45 (we recommend using the most recent available version), and it must be the extended version, which supports SCSS.

  2. Fork the Amybo pages repo repo into your own project, then create a local copy using git clone. Don’t forget to use --recurse-submodules or you won’t pull down some of the code you need to generate a working site.

    git clone --recurse-submodules --depth 1 https://github.com/Amybo-org/pages
    
  3. Run hugo server in the site root directory. By default your site will be available at http://localhost:1313/. Now that you’re serving your site locally, Hugo will watch for changes to the content and automatically refresh your site.

  4. Continue with the usual GitHub workflow to edit files, commit them, push the changes up to your fork, and create a pull request.

Creating an issue

If you’ve found a problem in the docs, but you’re not sure how to fix it yourself, please create an issue in the Amybo pages repo. You can also create an issue about a specific page by clicking the Create Issue button in the top right hand corner of the page.

Useful resources


5 -

1x Pioreactor 20ml 1x 12V peristaltic pumps 1x 5mm LED cables 1x LED 1x A raspberry PI (we have a Raspberry Pi 4 Model B - 8GB RAM doing nothing anyway) 1x Micro SD card 1x Raspberry PI power connector 1x Reagent bottle 1x Effluent reception bottle 1x Innoculum 1x Innoculum loop