Commercial and technical answers.

The annual subscription gives one licensed user access to the complete MainChain environment: the web GUI, API access and platform services. It covers digital asset management, manufacturing rights, workflow orchestration, production monitoring and authorised execution records.

The complete PaaS licence is £5,000 per user and per year. For education, the licence is £500 per teacher and students receive free access within the licensed teaching environment.

No. API-only plans are a separate entry point for organisations that want to integrate MainChain functions into their own application without using the MainChain GUI. A PaaS licence already includes API access, while an API-only subscription is billed according to its plan and token allowance.

A standard production workflow consumes 10 tokens, corresponding to the principal steps required to register, govern and follow the workflow. Each API plan includes a defined allowance, so teams can select a capacity aligned with prototypes, laboratories, business applications or industrial-scale operations.

No. Catalog Agent and Edge Server are paid sub-licences available only to customers with an active MainChain PaaS environment. Catalog Agent imports controlled plans from desktop and mobile devices, while Edge Server connects production equipment to the governed MainChain network.

Yes. Every printer or production machine communicates with MainChain through a licensed Edge Server. It acts as the controlled bridge between the customer environment and the equipment, applies the authorised workflow and returns production statuses without exposing the machine directly to the platform.

Compatibility depends on the machine interface, the available connector and the required level of production control. MainChain can support different additive manufacturing technologies through approved connectors, but each deployment is qualified with the customer and always uses the mandatory Edge Server.

The Marketplace brings together industrial 3D equipment, materials, consumables, services, qualified production capacity and complete customer-published systems. A drone, for example, can combine a structure produced through MainChain with batteries, motors, a flight controller, an IMU, cables and a pilot console sourced through the Marketplace before assembly and delivery.

The asset owner defines who may access or manufacture an asset, in which territory, during which period, on which qualified machine and in what quantity. MainChain carries those permissions through the workflow and records authorised evidence, timestamps, statuses and metadata for audit and accountability.

The proof infrastructure does not store the transmitted industrial binaries. It records the authorised verification evidence, timestamps, workflow statuses and permitted metadata needed to maintain a verifiable operational history while the industrial content remains under the control of its owner and authorised systems.

MainChain supports public cloud, private cloud and sovereign on-premise operating models. The choice depends on security policy, network isolation, data governance, interoperability requirements and the operational constraints of the programme.

Yes. MainChain-supported workflows have contributed to more than 20,000 produced parts and have operated across naval vessels, overseas bases, private clouds and interoperability environments. Deployment design and claims are assessed against the exact customer scope and operating conditions.

The first step is an operational briefing covering the digital assets, users, production sites, target machines, security constraints and integration points. The team then defines the appropriate subscription, deployment model, Edge Server topology, connectors and initial governed workflow before wider rollout.