Lab · Ersher · In development
A website address in, a runnable copy out
A website is tied to wherever it was first built. Moving one, rebuilding it, testing a change safely or bringing it inside a governed delivery pipeline takes weeks of hand work, and how it fits together usually lives in one person's head. Ersher is specified to take a URL and produce a self-contained, containerised version of that site that can be run, inspected and worked on anywhere.
Where it is up to
Specified in detail
What it takes in, what it produces, and how a container is handed to a project team are written down. The build starts from a specification rather than from a prototype that has to be argued with afterwards.
design completeWaiting on two foundations
Ersher runs on the Decision Bus and the Project Layer as core infrastructure, so it starts once the hardening of those two is finished. Building it first would mean building it twice.
by designIts place in the pipeline
It is planned as the front door of AI-supported work: you bring a URL, and the governed pipeline takes it from there, with every step planned, signed off and on the record.
how a project startsWhat you can buy today
Website, AI and accessibility work delivered through the Decision Bus and the Project Layer. Bringing us a URL is the planned way a project starts; today it is a first conversation.