Skip to main content
Railyard
DocsLearnAPI reference
OverviewVideo tutorials
Getting startedThe estate modelRacks & rack typesDevices & the libraryStore roomDevice rolesStructured cablingPower & thermalDesign reviewCollaborationExportPlans & billingKeyboard shortcutsAPI & MCP
Ask / report a bug ↗Roadmap ↗

Collaboration

Design the same estate together, live.

Real-time editing

When your organisation shares a project, teammates edit the same estate at the same time. Edits stream between everyone in the room and merge live, so there is no emailing spreadsheets back and forth and no “who has the latest version”. Undo and redo stay personal — undoing rolls back your own changes, not a colleague's.

Live collaboration comes with Team and Partner (and every server running without billing). On other plans one person edits at a time; see Plans & billing.

If concurrent container moves would create an invalid tree, Railyard rejects the conflicting change, restores the shared hierarchy and retains your other pending edits. A notice explains the conflict so you can retry against the updated structure. After recovery, your undo history starts afresh.

Undo and redo also check the current tree. If another edit now depends on the change, the action is refused with a notice and stays in your history so you can resolve the dependency and retry.

Presence

You can see who else is in the project and where they are looking — down to the estate level and even the device or cable they have selected — so it's obvious when two people are working the same rack. If your connection drops, Railyard reconnects and resyncs automatically.

Roles

Access inside an organisation is governed by three roles:

  • Owner — full access, plus managing members, invitations and billing.
  • Editor — can change designs.
  • Viewer — read-only; the app shows a view-only banner and disables editing.

Roles are enforced on the server, not just hidden in the interface, and one organisation can never read or write another's data. See the Security page for the full detail. Viewers are free on every plan and never take an editor place. Team includes 5 owner/editor places and unlimited viewers; additional editors are billed. Owners can choose £199 monthly or £1,990 yearly for the Team base, then £35 monthly or £350 yearly for each additional editor. Pro, for one designer in a personal space, is £49 a month or £490 a year.

Sharing

Share in the left rail opens the Share menu. In a hosted project it lets an organisation owner invite someone by email (and a project administrator give a member a role on a private project), copies the live project link for teammates, and downloads the project as a JSON file. Without a server it offers the JSON file.

The project link opens the live project only for people who already have access to it, and removing their role or membership stops it working. To share a live, revocable view with someone new, invite them to the organisation as a viewer.

Download JSON (also in Export) saves the whole design — every space, rack, device, cable, power link and diagram — as a Railyard project file. The recipient opens it with Open project file (see Getting started), which creates a separate copy. Treat the file like any exported copy of the design: it does not update with later edits, and once sent it cannot be withdrawn.

Deleting and restoring

Deleting a project or an organisation takes it away from everyone at once — from the projects page, links, search, the API, personal access tokens, AI connectors, exports and live editing. Anyone who has it open is told it was deleted and leaves it. Nothing is lost straight away: it stays restorable for 30 days, then it is deleted permanently.

  • A project is restored by its administrators (organisation owners, for a project the organisation can see) from Organisation settings › Recently deleted. It comes back exactly as it was, with its access settings, history, branches and field links. If another project has taken its name in the meantime, it comes back as “name (restored)”, which you can rename.
  • An organisation is restored by its owners from Account settings › Data & deletion › Recently deleted organisations, with its members, invitations, projects and plan. If another organisation has taken its name, it comes back as “name (restored)”.
  • Delete permanently in the same list removes it at once, after you type its name. That can't be undone. Deleting your account also permanently deletes any deleted organisation you alone own.

A deleted name is free straight away, so you can create a new project or organisation with it. Recently deleted, restoring and permanent deletion work only when you are signed in to Railyard in the browser, never with an API token. An organisation whose paid plan is set to renew can't be deleted; cancel the plan in Billing › Manage billing first. Restoring doesn't charge or resubscribe it.

RailyardRack layouts, topologies, cabling and capacity — in one place.
DocsLearnAPI referenceFeedbackRoadmapTermsPrivacyDPASecurityAccessibilityContact
© 2026 Railyard Tech Ltd · Railyard · Railyard is a trading name of Railyard Tech Ltd, registered in England and Wales no. 17525277, 24 Elizabeth Road, Wokingham, England, RG40 1UB