The Janitor is tied to The Facility and its Gunk, Machine, and Data themes. Treat every offer as a link in a working chain: an immediate action, a way to generate or move a resource, or a payoff that already has support. Do not add a support card only because it belongs to the theme.
Start with the official boundary.
Team Lazerbeam's Early Access material places the Janitor inside The Facility theme and names Gunk, Machines, and Data together. The launch post also confirms that every launch character has a distinct Combat starting deck, Explore starting deck, and base Foresight card.
Read the three-resource chain.
The following working definitions come from an unofficial build-scoped reference for Steam public build 25221077. They are useful for reading a run, but they are not developer-authored rules text.
A cost and scaling pressure attached to cards. Some effects care about removing, storing, consuming, or counting it.
A bridge resource used by Machine effects. Data without a relevant Machine can become delayed value instead of immediate help.
The payoff side of the chain. A Machine offer is easier to justify when the run already creates Data reliably.
A current Facility run also shows Decay, turrets, feeding, and healing decisions around this core. Those systems may interact, but one video is not enough to declare a fixed Janitor archetype.
Ask three questions before adding a card.
- Does it help now? Identify the action it performs before counting a future combo.
- Does the bridge already exist? A Data payoff needs Data; a Gunk payoff needs a controlled way to carry or remove Gunk.
- What happens when you miss the payoff? If the answer is “the deck draws another support card,” the offer may increase deck bloat.
This is an editorial decision framework, not a hidden game formula. It is designed around the questions visible in current Janitor runs and community discussions.
One current run shows where the plan bends.
Zueljin Plays published a Janitor/Facility run on September 10, 2026. Its creator-supplied chapters provide useful checkpoints without turning the run into a universal walkthrough.
Starts at the creator's Data and Machines chapter. This is one recorded run, not a guaranteed build recipe.
| Time | What the run is considering | Question to carry into your run |
|---|---|---|
| 00:08 | Data powering Machines and experiments | Do you already have a payoff, or only a resource? |
| 00:16 | Flame Turrets, Syringes, and early Gunk | Which offer produces useful value immediately? |
| 00:56 | Toad experiment and deck thinning | Which weak or stranded card is reducing draw quality? |
| 01:28 | Clean Freak versus Data Miner pivot | What does the deck already support strongly enough to commit? |
| 02:25 | Final-boss discard pressure ends the run | Can the deck recover when the ideal sequence is interrupted? |
Keep watching here: the embedded player stays on this guide, so the checkpoints below remain available while you follow the run.
Current players are asking about consistency.
A September 12 Reddit discussion centers on deck bloat, healing pressure, Facility boss difficulty, and uncertainty about Gunk, Machine, Data, and Decay payoffs. Other commenters report successful turret/Data or Gunk-scaling runs, including one-shot and loop outcomes.
That disagreement is useful: it suggests the page should explain prerequisites and failure conditions, not publish a single tier-list answer. It does not prove that Janitor is underpowered, overpowered, or solved.
What this guide will not pretend to know.
- The exact Janitor starting Combat and Explore decks.
- The exact quest chain that unlocks the Janitor or The Facility.
- A guaranteed infinite loop or a universal best build.
- A fixed Facility map, Boss order, or final-boss script.
- That every packaged card record is obtainable in a normal run.
Sources and version notes.
Official: Team Lazerbeam Early Access dev diary at 05:27–05:45; September 10 launch announcement; Steam store.
Build metadata: SteamDB public branch, showing build 25221077 when checked September 13, 2026.
Unofficial reference: NiaMeowDB, used only as a build-scoped research index.
Player examples: Zueljin Plays Facility run and the linked Reddit discussion. Neither is treated as developer documentation.