Martin Brown operates a professional film lab built around multiple AGO units running as distinct process cells. In this piece, he explains the infrastructure reasoning: how a decentralised AGO architecture keeps chemistry routes separate, gives ECN-2 its own process path, and turns genuine process choice from a promise into a practical operational reality.

If a film lab is built properly now, with access to better chemistry, more specialist films, stronger scanning, and far more process knowledge than older retail lab models ever exposed, what should clients actually be offered?

That was the question behind the build of Liquid Light Lab. The answer was not one fixed process lane or one centralised machine environment deciding everything downstream. It was a decentralised processing architecture built around choice: the right chemistry for the film, the right process for the result, and the freedom to keep distinct workflows distinct. AGO became the core platform because its process range, portability, modularity, and firmware-led development made that kind of lab possible.

From the start, the aim was to keep meaningful process decisions open. Chemistry is not hidden behind broad service labels. Different films are not collapsed into one general route. The architecture allows separate process paths to remain separate, while giving the lab the flexibility to expand, refine, and assign the right workflow to the right film.

Building Around What Clients Should Actually Be Offered

A modern lab should not begin with the question of what one machine can accommodate. It should begin with the question of what the client should genuinely have access to when sending film for processing today.

That means access to better chemistry choices, more suitable process paths, stronger handling of specialist films, and scanning that respects the structure of the negative rather than flattening it into a general service outcome. It means a lab should be free to choose the right route for the film in front of it, not forced to reduce everything to the narrowest common denominator of one centralised workflow.

That is the principle behind Liquid Light Lab. The lab was built so that the process could fit the film, rather than the film being made to fit one pre-defined machine lane. AGO made that possible because it allowed the lab to be structured around flexible, decentralised processing from the outset.

How the Cell Model Changes the Structure of a Lab

Liquid Light Lab operates what I call the cell model, but these are not single-purpose stations locked forever to one chemistry. They are multi-process cells within a decentralised multi-unit architecture.

That distinction matters because it changes what the lab is able to do. One AGO unit can be running C-41 while another handles true ECN-2 and another runs 510 Pyro for black and white. One colour cell can be pushing while another is pulling. A further unit can be assigned to a different black and white developer when a different result is required. The system keeps these process paths separate in operation while remaining flexible in how each cell is assigned.

This is where AGO becomes far more than a compact processor. Used this way, it allows a lab to move away from one central machine environment and towards a distributed structure with real process separation. That in turn allows the lab to preserve choice, maintain distinct chemistry routes, and run multiple workflows in parallel without forcing them back into one shared logic.

Why Better Chemistry Starts with Better Infrastructure

Chemistry shapes the negative, and the negative shapes everything that follows.

This is easy to lose sight of when process language becomes too broad. C-41 sounds clear enough to most clients, and black and white sounds clearer still, but those labels only describe the broad family of the process. They do not describe the quality of the chemistry, the control standard behind it, or the level of intent in the way it is being used.

C-41 names the process family, not the quality of the chemistry. Black and white names the medium, not the developer.

That distinction matters because not all C-41 chemistry is the same in practice, and not all black and white developers render the negative in the same way. Change the chemistry and you change the image structure, the density behaviour, the tonal separation, and the scan that follows. Once that is understood, the infrastructure behind the lab has to leave those decisions open. A decentralised architecture of multi-process cells does exactly that. It allows chemistry choice to remain active because the system itself does not close the decision down in advance.

That was one of the core reasons for building Liquid Light Lab on AGO. Better chemistry choices only remain possible when the lab itself is built to support them.

True ECN-2 Needs a Real Process Path

This becomes especially clear with motion picture stocks.

VISION3 remains VISION3 when it is loaded into a stills cassette. It does not become C-41 because the format of delivery has changed. The emulsion remains a motion picture negative stock, and a serious lab should be able to respond to that with a process path that treats the stock on its own terms.

That is why true ECN-2 matters. It is not a novelty and it is not a workaround. It is a serious stills service for a serious stock, and it deserves to exist as its own process path rather than being folded into a C-41 development category because that happens to be the easiest route through a centralised system.

A decentralised AGO-based architecture makes that possible because ECN-2 does not have to compete for space inside one fixed machine logic. It can remain a distinct route within the wider processing system, with the film handled according to what it actually is and the scan shaped accordingly. That is one of the clearest examples of what changes when a lab is built around process integrity rather than convenience.

Black and White Developer Choice Should Stay Open

Black and white makes the same point even more clearly because developer choice is directly visible in the result.

Black and white is not one generic process. The developer is part of the rendering. Change the developer and you change tonal separation, density structure, highlight behaviour, grain behaviour, adjacency effects, stain where relevant, and the way the negative behaves in scanning. Once that is understood, black and white can no longer be treated as though one broad label tells the whole story.

That is why Liquid Light Lab introduced 510 Pyro as a serious black and white option from the beginning. It was not there as a novelty and not there as a specialist flourish. It was there because developer choice matters, and because clients sending black and white film should be offered something more deliberate than a general backend route whose chemistry remains invisible.

A decentralised architecture is what allows that level of seriousness to remain practical. Once the lab is built on multi-process cells rather than one central lane, black and white does not have to collapse into one fixed answer. Different developers can remain real options because the infrastructure is flexible enough to assign different chemistry paths where needed while still keeping them separate in operation.

Multiple AGO Units Create Distributed Capability

This is not one compact processor doing every task in turn. It is a distributed processing architecture built on multiple AGO units working together as a coordinated system.

That is where the seriousness of the model becomes clear. The strength is not in a single unit considered in isolation. The strength is in what happens when several AGO units operate in tandem as multi-process cells across separate chemistry paths and separate workflows. That gives the lab concurrent capability, genuine process separation, and a level of operational freedom that a centralised single-machine model does not easily provide.

Used this way, AGO is not simply part of the workflow. It is the infrastructure of the workflow. Multiple units allow the lab to keep C-41, true ECN-2, 510 Pyro, push and pull workflows, and future chemistry paths within one coherent system without collapsing them back into one shared processing environment. That is what gives the architecture its depth.

Portability, Firmware, and a Platform That Can Keep Developing

Portability matters because it changes the relationship between the processing system and the work.

A central machine belongs to one room. AGO does not. Its portability means the processing capability itself is not locked to one permanent location or one rigid operational setup. That creates possibilities for location-based work, specialist assignments, demonstrations, and future service extensions that are much harder to achieve when the entire process is tied to one fixed centre.

Just as important is the fact that AGO is not static. Firmware and programme development mean the platform can continue to evolve. Instead of buying into one technical state and remaining there, the lab is built on a platform that can be refined, extended, and updated over time. That matters because a modern lab should not be trapped in the assumptions it started with. It should be able to improve its process routes, extend its service depth, and keep developing as the platform develops.

That combination of portability and updatability is one of the reasons AGO makes sense as serious lab infrastructure. It gives the lab freedom not only in how it processes film now, but in how it grows into what it can offer next.

35mm, 120 and Large Format

The same decentralised model of multi-process cells that makes serious 35mm processing possible can extend into 120 and large format without abandoning the principles on which the lab was built. The foundation does not need to be replaced. It needs to be extended.

That is another reason AGO made sense as the core platform. It was not chosen as a temporary answer or a compromise. It was chosen because it gave the lab a structure that could grow in capability and format range without collapsing into one general route as the service expanded. Growth should not require a lab to simplify itself. A strong architecture should support deeper service, broader format coverage, and further process development while keeping meaningful process choices alive.

A Better Client Experience Through Decentralised Design

A client-first lab is not defined by broad promises. It is defined by whether the architecture of the lab actually leaves room for better decisions to be made.

That is the central point of the AGO cell model at Liquid Light Lab. It keeps chemistry visible. It keeps process paths open. It allows ECN-2 to remain ECN-2, black and white developer choice to remain meaningful, colour processing to remain deliberate, and multiple workflows to run in parallel without being absorbed into one central machine environment. It allows portability where portability matters and firmware-led development where long-term improvement matters. Most importantly, it allows the service to be built around what the film and the client require, not around what one inherited system happens to make easiest.

That is what AGO made possible at the centre of Liquid Light Lab: a decentralised, modern, client-first lab architecture built around better chemistry, better process choice, better workflow freedom, and a better standard of service from the ground up.

By Martin Brown | Liquid Light Whisperer