Runbooks, Change Requests and the Change Board, on One Self-Hosted Platform
IT operations teams keep three things that drift apart over time: runbooks and policies in a wiki, change requests and vendor records in a tracker, and the week's work on a board. Nextcloud Hub Enterprise, operated by MassiveGRID, holds all three in one place you control: Collectives for the runbook library, Tables for changes and vendors, Deck for the stand-up board, each linked to the others.
The sample content is your content
| What the team keeps | Where it lives | What it looks like |
|---|---|---|
| Restore runbook | Collectives | Numbered steps, a code block and a warning callout |
| Change management policy | Collectives | A page under Policies, with backlinks to the runbooks it governs |
| Post-mortems and meeting notes | Collectives templates | Every incident review starts from the same structure |
| Onboarding | Collectives | A section of the handbook, with an @mention of the on-call buddy |
| Vendor register | Tables | Tier, country, owner, contract end and last review |
| Change requests | Tables | Category, status, requester, planned date, risk and a relation to the vendor |
| Awaiting approval, emergency changes, overdue reviews | Saved views | Filters that keep themselves up to date |
| The week's changes | Deck | Backlog, Awaiting approval, Approved, Scheduled this week, Done |
| Change windows | Calendar | Card due dates appear in the team calendar |
The runbook library, the records, the board and the controls
The runbook library 57 s
An IT Operations handbook with Runbooks, Policies and Onboarding sections, a database restore runbook with numbered steps, a code block and a warning callout, two engineers editing the same procedure at once, an @mention of the on-call buddy, backlinks from policies to runbooks, a meeting-notes template, version history with restore, search for "rollback" across pages, boards and files, and a security team member reading the handbook without edit rights.
Change and vendor records 49 s
A vendor register with tier, country, owner, contract end and last review, a new vendor added through a form, sorting by last review and filtering to critical vendors, a saved view of overdue reviews, a change-request table whose Vendor column is a relation to the register, sharing of the register with IT and of a single view with compliance, an application that groups vendor management for its owners, and CSV import.
The change board 43 s
Backlog, Awaiting approval, Approved, Scheduled this week and Done as lists, cards tagged Standard, Normal or Emergency with assignees and due dates, a firmware upgrade moved to Approved, the card's rollback plan, checklist, release notes attachment and a comment asking the on-call engineer to confirm the window, filters by tag and assignee for the stand-up, due dates in the team calendar, and the two-way link between the card and its row in the change-request table.
What the operations team runs underneath 46 s
SSO through the directory with MFA at the provider, groups mapped from SAML attributes, a leaver suspended in the directory and refused on the next login, sharing policy set once for the instance, audit events shipped to the SIEM by syslog, nightly backup with a measured restore to a standby host, and the administration overview with all sovereignty checks passing.
How the three link together
A firmware upgrade starts as a row in the change-request table, with its vendor picked from the register through a relation column. Its card on the change board carries the rollback plan, a checklist, the release notes as an attachment and a comment asking the on-call engineer to confirm the window. The card and the row link to each other in both directions.
When the change is approved the card moves to Approved, its due date shows in the team calendar, and the runbook it follows is one click away in the handbook. Search for "rollback" and you get the runbook page, the card and the release notes in one result list.
Cards are tagged Standard, Normal or Emergency and filtered by tag and assignee for the stand-up. The register is shared with IT, and a single view of it, overdue reviews, with compliance.
The controls the same team will operate
For MSPs: the structure repeats per customer
A managed service provider keeps the same three things for every customer. A collective per customer holds its runbooks and network notes, an application in Tables groups its asset and vendor registers, and a board carries its changes. Groups decide which engineers see which customer, and a customer contact can be given read access to their own handbook and nothing else.
MassiveGRID operates the platform, so the MSP does not carry another system to patch. If you also want the monitoring and response side covered, see NOC services, SOC services and DevOps support.
Which plan fits
Collectives, Tables and Deck are part of the Nextcloud Hub Business and Enterprise plans, from $12.90 per user per month for 1 to 50 users, ordered online with the first month at $1. A team of ten runs its whole operations handbook that way.
For SSO, directory groups, the syslog audit feed and your own sharing policy, take a dedicated Nextcloud Enterprise instance (single tenant, from 50 users, on your own domain); the calculator is on the managed Nextcloud hosting page. Leaving Confluence and Jira at the same time? See the Confluence and Jira alternative.
Nextcloud Hub Plans for an Operations Team
Collectives, Tables and Deck are included from the Business plan. Pick the region, set the number of engineers and order online; the first month is
Nextcloud Hub Plans for an Operations Team
.First month for $1 on monthly billing with coupon code NEXTCLOUD, applied by the Order buttons.
- Files, Photos, Calendar and Contacts
- Nextcloud Office: documents, spreadsheets and presentations
- Talk: chat, audio and video calls, screen sharing
- Standard Email
- 100 GB storage per user
- Desktop and mobile sync clients, public share links
- Nextcloud Enterprise platform with managed updates and daily backups
- Ticket support
- Files, Photos, Calendar and Contacts
- Nextcloud Office and Talk: documents, chat, audio and video calls
- Notes, Collectives, Tables, Deck and Tasks
- Standard Email
- 1 TB storage per user, ten times Starter
- Desktop and mobile sync clients, public share links
- Nextcloud Enterprise platform with managed updates and daily backups
- Priority support: faster response and escalation
- Files, Photos, Office, Talk, Calendar and Contacts
- Notes, Collectives, Tables, Deck and Tasks
- Enterprise Email with delegation and other enterprise mail features
- 1 TB storage per user
- Desktop and mobile sync clients, public share links
- Nextcloud Enterprise platform with managed updates and daily backups
- 24x7 support
- Upgrade path to a dedicated instance with your own domain and branding
USD per user per month before taxes; the billing-cycle discount applies to every plan. Order 1 to 50 users online. Need your own domain, a compliance boundary of your own or more than 50 users? See the dedicated instances below or contact us.
Frequently Asked Questions
Put the Runbooks Next to the Changes
Start a Business plan for $1 and move one runbook, one register and one board. The rest follows the same pattern.