My Firefox container setup. Keeps the heavy trackers and big platforms out of everyday browsing.
Find a file
2025-11-29 09:58:37 +13:00
.gitignore Containerise rules and documentation 2025-11-28 12:29:25 +13:00
changelog.md Containerise rules and documentation 2025-11-28 12:29:25 +13:00
containerise-rules.min.txt Containerise rules and documentation 2025-11-28 12:29:25 +13:00
containerise-rules.txt Containerise rules and documentation 2025-11-28 12:29:25 +13:00
LICENSE Containerise rules and documentation 2025-11-29 09:58:37 +13:00
LICENSE.html Containerise rules and documentation 2025-11-28 12:29:25 +13:00
readme.md Containerise rules and documentation 2025-11-29 09:58:37 +13:00

Firefox Containerise Rules

This repo stores my domain routing rules for the Containerise extension for Firefox. It works alongside Firefox Multi-Account Containers (MAC). MAC provides the containers and visuals. Containerise handles the routing with regex patterns.

The goal is simple. Stop cross-site tracking by forcing high-risk sites into their own containers. This isnt because I visit these services often. Its to contain the privacy leak when I land on them by accident or through a link I didnt check.

These rules isolate Google, Meta, Amazon, Microsoft, financial services, social platforms and streaming services. Ive included the major and smaller NZ banks as an example to organise your banking services, and kept them separate from popular fintech and payment services. The Personal container is empty on purpose. It gives you a neutral space you can use for general browsing, or for sites you dont want pushed into one of the automatic containers.

How to use

  1. Install the Containerise extension for Firefox.
  2. Install Multi-Account Containers (MAC).
  3. In MAC, create each container you plan to use and customise the colour and icon. Container names must match the names used in containerise-rules.txt.
  4. Open the Containerise options page.
  5. Copy the contents of containerise-rules.txt into the rules field.
  6. Save.
  7. Leave MAC's "Always open in this container" lists empty so Containerise controls all routing.
  8. Use MAC manually when needed. Right click a link or tab and choose Open in Container to override the automatic routing.

My setup

  • Containerise handles all automatic routing using regex patterns. It decides which domains open in which container, so you dont need to maintain site lists manually.
  • Firefox Multi-Account Containers manages the containers themselves, including the colours and icons. By leaving MACs site lists empty, you avoid clashes and let Containerise act as the single source of truth.
  • MAC is still useful for manual overrides. If you want to force a link or tab into a specific container, right click and choose Open in Container.

Ideas for containers

  • Personal
  • Banking
  • Finance
  • Google
  • Microsoft
  • Meta
  • Amazon
  • Twitch
  • Twitter/X
  • Reddit
  • Shopping
  • Streaming
  • AI Tools
  • Social

Config file

The file containerise-rules.txt contains the full rule set.

Format:

@domain-regex , Container Name

Containerise strips comments and sorts the list automatically when you import it. This repo keeps the formatted version intact so it is human readable and easy to maintain.

Why use containers?

Firefox containers dont fix the surveillance web, but they reduce the blast radius. One accidental visit to Facebook, YouTube, Reddit or any AWS-hosted service wont leak into the rest of your browsing. Identity stays isolated. Cookies stay fenced in. Tracking systems have less to work with.

If you want to adapt this for your own setup, copy the file and swap domains as needed.

Licence

MIT. See LICENSE.