Notes from the Createrun engineering team.

Architecture deep-dives, platform decisions, and the occasional opinion. Written for engineers, partners, and customers who want to understandwhythe platform looks the way it does.

Longer-form essays and editorial content live onblog.createrun.ai— a dedicated reading surface separate from the engineering changelog.

CORNERSTONE POSTS
AI · ENGINEERING

Why we built our own MCP server (and what it does)

2026-05-08 · 9 min read

Most low-code platforms are bolting LLMs onto code-completion and calling it AI. We wanted something different: an AI agent that could actuallyauthorour platform's artifacts — forms, queries, workflows, BPM flows — through a typed, validated, batched protocol. That meant building our own Model Context Protocol server. Here's the design, the trade-offs, and what we shipped.

Read post →
PLATFORM · OPINION

On-prem in 2026: when low-code makes sense

2026-05-08 · 7 min read

The narrative says everything is moving to SaaS. The reality, especially in regulated industries and emerging markets, is more complicated. Data residency rules, sovereignty concerns, supplier audits, KVKK / GDPR enforcement — these don't get cheaper as you move to someone else's cloud. Here's when on-prem is the right answer for a low-code stack.

Read post →
SECURITY · MARKETPLACE

Marketplace dual-signature explained

2026-05-08 · 6 min read

Why does the Createrun Marketplace sign every CRApp twice? Because one signature only proves authorship — it doesn't prove anyone reviewed the package. We use developer + Store ECDSA P-256 dual signatures to make tampering detectable from the moment a package leaves our review queue. Here's the threat model and the implementation.

Read post →
SUBSCRIBE

Monthly digest. New posts, release notes, and the occasional design deep-dive worth reading. Newsletter — planned. For now, follow ourTwitteror check thechangelog.