Every client's Linux servers, run from shared plans, each change approved by that client, with the record they keep.

For managed service providers that run Linux servers for clients. Your engineers keep the tools they use and run the same plans for every client, so routine work no longer starts from one person's shell. Opafra adds the approval your client gives, the window their access runs for, and a record each client can keep.

Your client approves

A change waits for the client's own approver, who sees the revision it covers.

The approval is recorded with the approver's name and the revision, and it is void if the plan is edited afterwards. The approver must hold access to that environment, and the environment comes from the hosts the plan targets.

Fig. 1, the approval request for revision 7 in prod

Patch nginx across prod

Upgrade nginx to 1.25.3

blocked 2mweb-01, web-02, web-03console4 items

@alex → AIDry-run passedApproval requiredAudit

Revision: Covers revision 7 only.
Targets: web-01, web-02, web-03 in prod, derived from the targets
Approver: Must hold access to prod

Client view

Each client's servers, plans, runs and records, seen one client at a time.

Work across all your clients from one place, and open a single client to see only its servers, plans, runs and records. What you ran for one client is never mixed into the view of another.

Client onboarding and handover

Onboard a client from a template, hand over with the record.

Onboard from a template: Start a new client from a template of the plans you already run for others, not from an empty account, and change what differs.
Hand over with the record: When the engagement ends or moves to someone else, the client keeps the audit log of what was changed, by whom and on whose approval, as CSV or NDJSON.

One organization per client

Three things stay with the client, whatever else you run for others.

The details are on the security page, and the same isolation is described for consultancies.

Its own organization: Each client has its own encryption key, SSH certificate authority, members and audit log. What you did for one client never sits in another client's record.
Its own approver: A change to the client's servers waits for the client's own approver. Client-side viewers and approvers are included in every plan, so your clients do not pay to approve.
Its own export: The audit log exports as CSV or NDJSON, so the client can keep the record after the contract ends.

The record each client keeps

What changed, by whom, and on whose approval.

Each run writes its entries to the client’s append-only audit log. Access to the servers is on the same record: see supplier access and the evidence page.

Fig. 2, the audit entries run #4f2a wrote

Audit log /run #4f2a

Append-only5 entries

The audit entries run #4f2a wrote, newest first
Time	Actor	Event
14:33:19	web-03	reloaded nginx
14:32:07	dana	approved revision 7
14:29:40	alex	dry run on 3 hosts, 12 changes
14:28:55	AI	drafted 4 steps for alex
14:28:31	alex	requested Patch nginx across prod

ExportCSVNDJSON

Good to know

Partners, scope and limits, stated plainly.

Partners: Managed service providers can refer or resell Opafra on written terms. See partners.
Built for Linux servers: Opafra connects over SSH, so it is built for Linux servers. A provider whose estate is mostly Windows will not find its tools here.
What is not in the record: Opafra records what goes through Opafra. Work done on a client server by another route is not in these records.

Run client servers on the record.

Tell us how many client estates you manage and who approves changes on them. You get a demo and your price in writing within one business day, with no call.

Get a demo