Skip to main content

Saving and sharing

Your models​

Ctrl+S, or enable autosave in settings. Saved models appear on your dashboard, where you can search, rename and delete them, and see at a glance which are private and which are public.

Private or public​

Every model is private by default. The visibility toggle in the editor toolbar makes one public — and asks you to confirm, because publishing is visible to everyone and not something to do by a stray click.

Publishing puts the model in the community gallery under your display name (set it in Settings, or it defaults to your email prefix).

Read it before you publish

A model can carry more than types: namespace URIs with a customer's name in them, browse names matching an unreleased product, descriptions written for internal readers. Publishing is a deliberate act — the confirmation step is there to make you look once.

opcua-modeler.sterfive.io/community ↗

Public models from everyone, searchable by model or author.

Fork copies one into your own account. The copy records what it came from and who wrote it, so attribution survives — a forked model shows its original rather than pretending to be new work.

Forking is the fastest way to start something close to a model that already exists, and the fastest way to understand an unfamiliar pattern: fork it, break it, watch what the validator says.

Getting a model out​

The dashboard and editor keep models in your account. To take one elsewhere:

  • Download bundle in the Dependencies panel — the model plus the nodesets it imports.
  • The REST API — generate NodeSet2.xml, Symbols.CSV and documentation with an API key.
  • The desktop CLI — the same, offline.

Models are plain YAML and NodeSet2 throughout. Nothing here is a format only we can read.