Publish your application to the Createrun Store.

Package it in the Editor, pass review, and make signed versioned updates available to customers on their own or managed servers. Publish free apps under your own publisher profile.

Become a publisherBook a demo
FIND APPS

Looking for apps to run? Browse the Createrun Store and install what your team needs on the instances you control.

Browse the Store 

Pipeline

From the Editor to a live install in four steps.

The publisher journey connects development, signing, review and installation for supported Createrun packages. An arbitrary repository from another technology stack does not become a Store package automatically.

Build

Build with the Editor, supported AI operations or code extensions, then package the Createrun application for distribution.

Versioned package

Sign

You sign the package with your publisher key, which proves who built it and that nothing in it has changed since.

Publisher signature

Review + publish

The Createrun Store runs its documented review, adds its own signature and publishes the package to the catalog. That signature confirms package integrity and Store approval. A line-by-line security audit of the application code is outside the review's scope.

Store-verified release

Install + license

Each instance checks both signatures at install time and receives a license issued for that specific instance.

Instance-bound license
PACKAGE SECURITY

Two signatures, checked before anything runs

Every package is signed twice, by the publisher and by the Createrun Store, and both signatures are verified before the package can run. If anything was altered between those two points, the install fails before any package code executes.

How package security works →

Licenses that stay where they were issued

A license is issued to one instance and checked when that instance starts, so a copied license does not run anywhere else. Renewals and revocations propagate to the instance on their own, and a failed platform upgrade rolls back automatically.

Read: Createrun Store dual-signature explained →

UPDATE LIFECYCLE

Updates on a schedule the customer controls

Instances check the Createrun Store for new versions of the applications they run and install them through the same signature-checked, dependency-aware path as a first install. A publisher ships a release once; the Store offers it to each instance, and the customer decides when to install it. Updates are staged before they apply, with best-effort rollback, and Createrun opens no inbound connection to your servers.

You choose the version each instance runs

You control which version each instance runs and when it moves to the next one. A staged package can be discarded before it applies, and recovery after a failed install is best-effort. Plan backups and test recovery for your application data and external integrations.

PARTNER PROGRAM

A catalog listing makes an application discoverable; it does not guarantee customers or sales. Publishers own their product's support and compatibility work.

Develop an application for customers and partners.

Solution Partners use the same distribution channel as every app in the Createrun Store. Createrun handles review, signing, license issuance and update distribution for a published app. Book a demo to discuss publisher access and review requirements.

Build and sign

  • Author the application in the Editor
  • Sign the package with your publisher key
  • Choose a license model

Review and distribution

  • Store review and a second signature on the package
  • A license issued to each installing instance
  • Signed updates that instances fetch on the customer's schedule
  • A listing in the public catalog

Ownership

  • Free apps published under your own publisher profile
  • Your product and roadmap stay yours; project files and custom source authored by you or your AI remain yours
  • The customer relationship stays with you
Book a demo

Looking for a specific solution?

Tell us the application you want to build or distribute. We can discuss the project scope and available partner routes, including which parts need custom development.

Book a demo