Three parts, each with a clear job.

MP-Opt separates local planning, schedule publication and evidence verification. A small event can use only the Desktop; a self-hosted deployment can add the Server and evidence workflow when those responsibilities are needed.

The components

Use the pieces that match the event and the operator’s responsibilities.

Desktop

Plan and optimise locally

Build the event, describe the constraints and review the result on the planning workstation. Keeping the working project local protects the space where the team is still thinking and changing its mind.

Desktop source and releases

Server

Share an approved schedule

Publish the information people need through a responsive web calendar. The self-hosting operator carries access, governance and recovery so organisers and participants can rely on the schedule.

Server source and releases

Evidence

Keep an accountable record

Signed records preserve the statements and receipts added to an evidence chain. Public tools let another person verify that history offline without receiving private signing material.

Evidence tools and verifier

The boundary

MP-Opt can check the plan. The organising team still owns the decision.

MP-Opt can

Check constraints, suggest allocations, publish selected information and record exact technical actions.

People still decide

What information is necessary, which trade-offs are fair and whether a proposed plan is appropriate for the event.

Publishing choices

Share one reviewed schedule in the forms your event actually needs.

Choose any combination of the three destinations. MP-Opt uses the same reviewed day or set of ready days for the whole publication.

MP-Backend

An authenticated personal masterplan and a deliberately public participant schedule.

PDF

A light, portrait schedule with readable assignments and task details, saved locally.

Google Calendar

Optional calendar publication for events that choose to configure the integration.

Read the publishing guide

Availability

A second server can keep published access available.

Optional high availability replicates state between two independently hosted nodes and uses guarded failover for the public service.

Read about resilience

Recovery

External snapshots cover a different kind of failure.

Encrypted, independently stored snapshots are intended for corruption, operator error or the loss of both servers. Creating one is not enough; it also needs to be verified and kept elsewhere.

Read the snapshot guide

Start where you need to

Download the Desktop or open the guides.

Download Documentation