Enterprise DNA

Instead of CleanCloud

Stop renting CleanCloud. Own your laundry order system.

We build your version around your intake, plant and collection routine, bring your CleanCloud records across and run it for you. Start with the order workflow and scope the counter and driver tools your business needs.

CleanCloud lists Australian monthly-billing prices of A$135 for Lite, A$165 for Pro, A$235 for Grow and A$520 for Grow+. Onboarding and optional extras are separate.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The CleanCloud bill

Your plan follows order volume and the features you need

CleanCloud combines a counter system with production, delivery and customer tools. Compare the parts you use with an order system built around your own routine.

paid

A monthly store subscription

Australian Lite is A$135 a month on monthly billing, or A$1,620 across twelve months at that rate. Annual billing has a different rate.

inventory_2

Order-volume allowances

Lite includes 500 orders a month, Pro 2,000 and Grow 3,000. CleanCloud says sustained use above the plan allowance leads to an upgrade discussion.

local_shipping

Pickup and delivery on Pro

Pro is A$165 a month in Australia on monthly billing. Its package includes pickup and delivery, a driver app and route tools.

layers

More automation on Grow

Grow is A$235 a month in Australia on monthly billing. It adds automatic assembly, automated invoicing and access for connecting other systems.

smartphone

Your branded app on Grow+

Grow+ is A$520 a month at the listed Australian rate. It includes a branded customer app and requires a minimum twelve-month commitment.

receipt_long

Onboarding and optional credits

CleanCloud names onboarding alongside the subscription as a core cost. Text-message and Journey credits are optional extras to check against your own bill.

The owned order workflow

Follow every piece from intake to handover

Production

Know what threatens a promise

See the pieces behind each late ticket and the records needed before work continues.

  • check Promised dates alongside the unfinished piece count
  • check Care-label and intake-condition records for each tag
  • check A separate list of pieces needing another clean
  • check Checks that require a rack position and the person who checked the garment

Collection

Find what is sitting on the rack

Follow ready work through to actual handover, with a history of the events staff record.

  • check Ready tickets ranked by time on the rack
  • check The customer and recorded balance for each ticket
  • check Collection reminders prepared as drafts for review
  • check Collection recorded separately from payment settlement

Delivery

Check the load before the driver leaves

Put the planned stops beside the work the plant has actually finished.

  • check Pickup and delivery stops in the order you set
  • check A visible warning when a delivery order is not ready
  • check Printable manifests with addresses and piece counts
  • check Confirmed handovers recorded without changing paid amounts

Your rules

Ask questions across the whole order history

Keep the questions, records and paperwork under your control as the business changes.

  • check Customer claims with an agreed follow-up date and recorded remedy
  • check Care-record checks and sourced NZ chemical-record checks
  • check Job tickets, garment tags, manifests and claim records in your business name
  • check Your own questions joining late work, unfinished pieces and collection history

Make it yours

Design your own CleanCloud replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from CleanCloud. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your CleanCloud replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your CleanCloud data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Laundry for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Laundry for Claude Code

Connected to your own database

Which tickets need our attention first?

HL-1003

Stomer st
Harbour Dental
Ore re
Harbour Laundry
Ason da
uncollected over 7 days
Ys
13

HL-1004

Stomer st
Leo Martin
Ore re
Harbour Laundry
Ason da
uncollected over 7 days
Ys
13

HL-1008

Stomer st
Harbour Lodge
Ore re
Harbour Laundry
Ason da
uncollected over 7 days
Ys
13

HL-1001

Stomer st
Aroha Bennett
Ore re
Harbour Laundry
Ason da
late production
Ys
6

HL-1002

Stomer st
Harbour Lodge
Ore re
Harbour Laundry
Ason da
late production
Ys
6

HL-1002

Stomer st
Harbour Lodge
Ore re
Harbour Laundry
Ason da
claim follow-up overdue
Ys
3

Ask it anything

Ten questions from your laundry records

These questions run against the free version today. Change them around the work your plant and counter need to see.

chat_bubble Which late tickets still have unfinished pieces?
chat_bubble Which ready tickets have been on the rack for a week?
chat_bubble Which delivery stops promise an order that is not ready?
chat_bubble Which customers have repeated open garment claims?
chat_bubble Which pieces need another clean and when are they due?
chat_bubble Which active pieces lack care or intake condition records?
chat_bubble What recorded balance is tied up in each store and currency?
chat_bubble Which customer remedy follow-ups are overdue?
chat_bubble Which chemicals lack safety documents or inventory details?
chat_bubble Which imported active tickets still need garment detail?

Switching

How to switch from CleanCloud

A move usually involves exporting customer and order records, mapping them to the new database, checking the results, then running both systems side by side before you stop using CleanCloud.

  1. 1

    Export customer and order records

    Export the customer and order records your account allows, usually CSV or Excel, and check the available format and fields with CleanCloud. CleanCloud confirms Excel exports for customers and orders, but the field headings are not fixed in a public format. Choose the history you need to bring across, and keep the original exports unchanged while the records are mapped.

  2. 2

    Test the import first

    Have the export headings and dates mapped before loading. The importer brings across customer records and order summaries, not full garment histories. Run the offered test import first so you can preview the records without writing them to the database. Review the result with whoever is handling the move, then load the records once the mapping looks right.

  3. 3

    Review and reconcile the results

    Compare the imported records with your CleanCloud exports and investigate anything the import flags. Reconcile the records before treating the new database as your working record. Garment detail, photos, payment credentials and message history need separate work, so identify which of those you need rather than assuming they came across.

  4. 4

    Run both systems side by side

    Keep CleanCloud available while you run the order workflow in Laundry for Claude Code for a short period. Use the same incoming work to check intake, production checks, racks, claims and delivery manifests, and compare the records your team relies on. Keep your existing POS, payment terminal and machine controls in place. This checks the order workflow, not a replacement for those systems.

  5. 5

    Switch off CleanCloud

    Once records are reconciled and your team has checked the new workflow against CleanCloud, make the new database your source for order work. Then arrange to stop your CleanCloud service with CleanCloud. Keep the POS, payment terminal and machine controls you still use, since Laundry for Claude Code does not replace them. Do not switch off CleanCloud before deciding how to handle history or other details that need separate work.

construction

Where the real effort goes

The work usually goes into mapping your export headings, dates, fields and operating rules, then deciding how much history to bring. The base import covers customer records and order summaries. Garment detail, photos, payment credentials and message history need separate work. If you have Enterprise DNA install and run it for you, Enterprise DNA handles mapping and reconciliation of your actual export as part of the move.

Not ready for a call?

Get your CleanCloud switch plan by email

We will send you the step-by-step plan for moving your business off CleanCloud, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, customise it, or have us run it

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and install its dependencies.
  2. 2 Run npm run demo, then open the folder in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Check the export guide, map your CleanCloud CSV headers and do a dry run.
  4. 4 Use a fresh database for your real records and verify garment detail before switching the workflow.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your garment fields, promise dates, rack rules and business paperwork
  • check Your CleanCloud export mapped and checked against the source records
  • check A counter screen, driver tools or a different technical foundation scoped around your needs
  • check Connections to your existing counter and payment systems agreed before the move
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Migration, database access and backups set up for your business
  • check Your order routine connected to the rest of the business where agreed
  • check Ongoing changes and support as stores, services and delivery runs change
Book a call with Sam

Questions

Instead of CleanCloud, answered

Does the free version replace our counter and payment terminal? expand_more

It runs the order workflow: intake records, production checks, racks, claims and delivery manifests. Keep your existing counter and payment terminal while that workflow is checked. Enterprise DNA can build the counter screen, driver tools and connections you need into your version as an agreed scope of work.

Can our CleanCloud history come across? expand_more

CleanCloud provides customer and order exports. The free version loads customer records and order summaries after the exported headings and dates are mapped. Garment detail, photos, payment credentials and message history need separate work. We inspect your actual export and reconcile the records before the move.

What will this cost us? expand_more

The base is free under an open-source licence. Hosting and any coding assistant you use have their own costs. Enterprise DNA charges one setup fee, then a retainer for the agreed customisation and ongoing service. Compare that scope with your complete CleanCloud bill, including the features you still need.

Can it check garment claims and safety records? expand_more

It flags missing care records, overdue claim follow-ups and gaps in recorded NZ chemical information. Each check has a source or is labelled as an internal operating rule. Your operator verifies the evidence and decides the next action. These checks do not certify the site or decide a legal remedy.

Can we put our own rules and business name on it? expand_more

Yes. Change garment fields, stages, collection reminders and the questions your team asks. Tickets, tags, manifests and claim records use your business name and colours. We can make those changes and run the system for you, or you can maintain your own version.

Build around the way your laundry works

Spend 30 minutes with Sam. Bring your CleanCloud bill and the steps a ticket takes through your plant. We will work through what to bring across, what to build and what it takes to run your version.

Book a call with Sam Get the free version

Laundry for Claude Code is free and open source, published by Enterprise DNA.

Done paying for CleanCloud?

Get your version built