An enterprise platform for building software and operating development.

Createrun supports two related kinds of work: developing applications on its framework, and operating a development environment on your own instance. Framework applications use Createrun services at runtime. Projects managed by the development tools can run on a different stack.

Start for free See the features

01 / APPLICATION DEVELOPMENT

Build on the Createrun framework

Model screens, data and workflows visually in the Editor. Use the Createrun Agent or supported operations from a compatible AI client through MCP. Write custom components, task objects, providers or GateMethods when needed; AppClient supports the framework project compilation workflow.

The project files and custom source you author remain reviewable and editable. Createrun compiles modeled application functionality into DLLs that use the Createrun runtime and remain subject to the applicable license.

02 / DEVELOPMENT OPERATIONS

Operate your own development environment

A Createrun instance can host tools for project knowledge, task tracking, and AI-assisted development. Your team can use those tools for projects built on Createrun or other frameworks.

The development tools run on Createrun; the software your team creates for another stack can run in its own environment.

Explore the tools and their roles

HOW THE PARTS FIT TOGETHER

Platform architecture

Building an application and running it are different steps. Your team works in the Editor, its own code tools, or a compatible AI client connected through MCP. The application you compile runs with Createrun services on your chosen instance; access and release controls govern the work.

01 / CREATE AND COMPILE

BUILD

Choose the tools your team uses to author a framework application.

Createrun EditorVisual models and the Createrun Agent in the Editor.

Your IDE + AppClientYour custom source and the required local compilation workflow.

AI client + MCPA compatible client connects to supported development operations.

COMPILED OUTPUTApplication DLLs

Modeled functionality becomes compiled assemblies. Custom source written by your team or its AI remains editable.

02 / DEPLOY AND OPERATE

RUN

The finished framework application uses the Createrun runtime.

ON YOUR CHOSEN CREATERUN INSTANCE Application runtime

Compiled application assemblies use the framework runtime and its services.

IdentityData accessProcesses

Publishing is a separate step

If you publish through the Store, the application travels as a signed package through a release review.

03 / CONTROLS THROUGH THE WORK

GOVERN

Access and permissionsUse scoped identities for people and connected tools.

Human reviewReview proposed Agent changes before applying them.

Release traceabilityReview and verify packages when publishing through the Store.

ANOTHER DEVELOPMENT PATH

Createrun development workspaceYour project on another stack

Project knowledge, tasks, and AI coordination can live on a Createrun instance while that project's software runs in its own environment.

WHAT YOU GET

01 · Build

Three doors into one application

Connect a compatible AI client through MCP, use the Createrun Agent inside the Editor, or work manually with visual designers and custom extensions. These paths work with supported application objects; operation coverage depends on the tool.

How teams build

02 · Run

A process engine that runs what was approved

Use process definitions to coordinate application work and place human decisions where your policy requires them. Execution history helps your team investigate a run; validate integrations and exception paths against your own acceptance criteria.

What runs in production

03 · Govern

Controls your change process already expects

Enterprise identity with single sign-on, role-based access, signed deployments, and an audit trail of who changed what and when, on your infrastructure or ours. Review the installed components and configuration for your instance.

Security controls

04 · The Createrun Agent

The Agent drafts; your team approves

You describe a change in plain language and the Createrun Agent drafts it. Your team approves the draft before anything ships. Each Agent action is recorded.

Meet the Createrun Agent

Four ways to work with Createrun.

Resell Createrun under your own brand.

Business Partners help organizations adopt and operate Createrun. Discuss deployment responsibilities, support, branding, and the current commercial agreement with the partner team before offering a service.

Build vertical solutions and sell them on the Createrun Store.

Solution Partners write applications for one industry (food production or real estate, for example) and publish them through the signed distribution pipeline. They keep ownership of their customizations and reuse the same application across customers.

Independent developers ship faster with the Createrun Agent.

Independent developers use Createrun as the back-office foundation for client work. Author visually or in your own code editor and hand the routine work to the Createrun Agent. You deliver finished applications to clients without rebuilding the basics, and the source stays with you.

Discuss referral opportunities.

Advisors can discuss referral opportunities with the partner team. Eligibility, tracking, and any compensation depend on the program agreement; a referral does not guarantee a closed deal.

Illustration of the Createrun Editor with a compiled C# file: the product Business Partners deploy and resell

Solution Partner storefront: a vertical application listed in the Createrun Store through the signed distribution pipeline

Developer workflow: professional code tools with the Createrun Agent scaffolding a form

Affiliate funnel: tracked link, qualified lead, closed deal, commission

Security that answers your auditors' questions.

Createrun was built for organizations that answer to auditors and regulators, and to their own security teams as well. The essentials are part of the standard install and documented in depth for the people whose job is to verify them.

✓ Application packages are signed by the publisher and verified before install
✓ Enterprise single sign-on with users and data scoped by organization
✓ Secrets are stored centrally and kept out of code and application packages
✓ Deployments are traceable, and staged updates offer best-effort rollback
Read the security page

Createrun security: signed packages, enterprise identity, central secrets, auditable deployments

Public sites: shared building blocks branded per customer site

Your public websites run on the same platform.

A Createrun instance can host multiple public-facing sites built from the same building blocks as your business applications. You lay out pages visually and brand each site per customer. Business users then edit content without touching the application underneath.

✓ Author each site once and brand it per customer
✓ Business users edit content live in a form-style editor, and that includes this marketing site
✓ Per-site settings drive SEO defaults, social tags, the sitemap, and robots.txt
✓ The site you are reading right now is built this way
Authoring features

Every app ships through the same pipeline

Apps in the Createrun Store are packaged and distributed through the same signed pipeline our publishers use, and every release stays traceable to its source.

Browse the Store

Publish under your own brand

Solution partners build vertical applications on Createrun and ship them through the same Createrun Store pipeline. License issuance and dual-signature distribution are built in.

Sell on the Store

DIGITAL SOVEREIGNTY

Project files and custom source authored by your team or its AI, compiled application DLLs, and business data are different parts of an exit plan. Your team can retain its authored work and manage data in its database. Framework dependencies and commercial terms still apply; evaluate the work required to run or migrate an application.

What you keep

Keep the project files and custom source you author, and manage business data in your database. Review and version changes in the tools your team uses.

What connects to Createrun

Modeled framework functionality is delivered as compiled DLLs that use the Createrun runtime. Activation and package downloads connect to Createrun; check licenses and dependencies in an exit plan.

Run it yourself

Fully on your infrastructure

Deploy on your own servers, whether that means your data center or your own cloud. The application runtime and process engine run on your servers; activation and package downloads connect to Createrun.

Own the source

Editable project files and custom source

Keep and extend the project files and custom source your engineers or AI author. Createrun delivers modeled application functionality as compiled DLLs; moving a framework application to another runtime requires a dependency and migration assessment.

Leave with your work

Data in a database you already administer

Business data lives in standard enterprise databases under your control, so your existing backup and retention policies keep applying and your DBAs keep their access rules.

Integration hub: identity, database, storage, and observability systems connect through providers; a payment provider is planned

Plug into the systems you already run.

OpenID Connect single sign-on runs through the built-in identity provider. Data stays in the enterprise databases and storage systems you already operate, and traces, metrics, and logs export to the monitoring stack you already run. Editions, additional cores and managed servers are sold in the Createrun Store. The Integrations page lists each provider with its current status.