Update content without deploys
Simple CMS alternative for UI text and copy
Store UI labels, marketing copy, and announcements in Replane. Non-developers update content directly from the dashboard—no CMS overhead, no deploy cycles.
Before & after Replane
See how teams transform their workflow
Without Replane
Hardcoded text
Fixing a typo requires a code change, PR review, and full deployment.
CMS overhead
Full CMS is overkill for simple text. Too complex to set up and maintain.
Engineering bottleneck
Marketing waits for devs to update copy. Simple changes take days.
Slow content updates
Can't respond quickly to events. Time-sensitive content goes stale.
With Replane
Externalized content
Store UI text in Replane. Update without touching code.
Lightweight CMS
Simple dashboard for text, no complex CMS infrastructure.
Self-service editing
Marketing and product teams edit content directly.
Instant updates
Changes go live immediately. Perfect for time-sensitive content.
Simple content updates
No CMS overhead, instant publishing
Instant Publish
Content goes live in under a second
No Deploys
Update content without code changes
Full Version History
Every revision saved and restorable
Self-Service
Non-technical teams can update content
Three simple steps
Get up and running in minutes, not hours
Define content configs
Create configs for UI text, announcements, and marketing copy. Use simple strings or structured JSON.
Integrate with your app
Use the SDK to fetch content. Components update automatically when content changes.
Enable self-service
Give marketing and content teams dashboard access. They edit, you focus on features.
Why teams choose Replane
Built for developers who value speed, reliability, and control
Instant publishing
Content updates propagate immediately via SSE. No waiting for deployments.
Version control
Full history of content changes. Rollback to previous versions with one click.
Preview before publish
Review changes in staging before pushing to production.
Works with your stack
Official SDKs for all major languages and frameworks
1import { Replane } from '@replanejs/sdk'23interface Configs {4 'hero-title': string5 'hero-subtitle': string6 'announcement-banner': {7 enabled: boolean8 message: string9 type: 'info' | 'warning' | 'promo'10 }11}1213const replane = new Replane<Configs>()1415await replane.connect({16 baseUrl: 'https://replane.example.com',17 sdkKey: process.env.REPLANE_SDK_KEY18})1920// Get content values21const heroTitle = replane.get('hero-title')22const heroSubtitle = replane.get('hero-subtitle')23const announcement = replane.get('announcement-banner')2425// Content updates automatically when changed in dashboard26replane.subscribe('announcement-banner', (config) => {27 if (config.value.enabled) {28 showBanner(config.value.message, config.value.type)29 } else {30 hideBanner()31 }32})
Questions about Content Management
Common questions and answers
Replane is much simpler. No complex content models, no database, no infrastructure to manage. Just key-value configs for your text content. Perfect when you need to update UI text but don not need a full CMS.
Yes! Store markdown or HTML strings in Replane. Your frontend renders them as needed. For complex layouts, consider a headless CMS—Replane excels at simpler content like labels, copy, and announcements.
Create separate configs for each locale (e.g., "hero-title-en", "hero-title-es"), or store a JSON object with all translations. Use override rules to serve content based on user locale.
Anyone you give dashboard access to. Role-based access control lets you define who can view, edit, or publish content changes. Marketing edits copy, engineering approves if needed.
Store image URLs in Replane, not the images themselves. Host images on a CDN or media service, then reference URLs in your content configs. This keeps Replane fast and focused.
Explore more ways to use Replane
Ready to ship faster?
Start using Replane in minutes. Free forever for self-hosted, or let us manage everything for you.
No credit card required. MIT licensed. Deploy anywhere.