The editor is hosted at, and uses URL parameters to configure its connection to your builder service.

You will host the SE2 builder service in your cloud infrastructure with a configured DNS name. An HTTPS connection to the builder is required to use the editor. To launch the editor, you can either embed the editor in a frame within your own webpage, or launch it in a new tab.

Editor Token

To authenticate the editor you’ll need an editor token.


The editor is configured with URL parameters. Here’s an example:

Let’s break it down:

Builder: ?builder=

  • This is the URL of your public builder service

Token: &token=K78as0aslwi30l8h5lbF4lS7

  • The editor token retrieved from the control-plane service

Ident: &ident=com.suborbital.customer

  • The identifier used when addressing your specific user

Fn: &fn=add-record

  • The specific plugin name that the editor should load

Namespace (optional): &namespace=default

The plugin namespace (if not included, the default namespace is used, see Namespaces for more details)

Template (optional): &template=assemblyscript

The language template used for new plugins. Check out our supported languages!

If the fn in question does not exist, the editor will automatically create a new extension.

Building and deploying

Once the user has edited their plugin, the build button in the top right will allow them to check to ensure the plugin builds. The builder service will build the plugin and then return the results to the console area.

Assuming the build succeeds, the user can choose to deploy the latest version with the deploy button. If they choose not to deploy, the draft will be available to them later.

Until the user deploys the plugin, it will remain at the previous version. The API Reference gives you details about the draft and active versions of any plugin.