Skip to content

Platforms & Migration

PLATFORMS & MIGRATION

Your kingdom.
Room to grow.

Build a business with a future beyond its first platform.

WordPress today. Native EmDash work in progress. Our own Winkdom CMS on the horizon. The ambition is a connected toolkit with more choice as your business evolves.

Purposeful technology.Connected business tools.Choice over time.

THREE FOUNDATIONS / ONE VISION

Choose what fits.
Know what is ready.

Your content, customers, and workflows matter more than a platform label. Start with the capabilities your business needs.

01 / THE FOUNDATIONCURRENT

WordPress
with Winkdom.

The home of the existing Winkdom plugin family. Bring design, publishing, customer relationships, commerce integrations, and support into a coherent site experience.

  • Builder and Theme shape the experience.
  • Choose business plugins around real needs.
  • InstaWP is our main WordPress cloud direction.

Products, editions, hosting connections, and individual features have their own availability and requirements.

Explore the toolkit

02 / THE NATIVE PATHIN DEVELOPMENT

EmDash.
A modern direction.

EmDash is a separate open-source CMS built with TypeScript and Astro. Its architecture includes isolated plugins and declared capabilities on supported runtimes.

  • Native Winkdom ports are being developed.
  • Migration work covers selected product data.
  • Support must be checked for each route.

A WordPress plugin does not automatically become an EmDash plugin. Native equivalents and data mappings are separate work.

Understand the move

03 / OUR NEXT CHAPTERPLANNED

Winkdom CMS.
Built for the whole.

Our own CMS direction brings the website, business toolkit, cloud services, and future app experiences around a purpose-built foundation.

  • Go for the intended application backend.
  • PostgreSQL for structured business data.
  • A serverless architecture designed for growth.

Architecture direction, not a generally available product or a release-date commitment. More platforms may be considered later.

Meet the intended stack

EmDash background: Cloudflare’s introduction to EmDash ↗. Winkdom integration readiness is separate from the CMS itself.

WINKDOM CMS / ARCHITECTURE DIRECTION

Strong foundations.
Less friction above them.

A considered stack connects a fast interface to reliable business data. Each layer has a clear job.

GO / EFFICIENT SERVICES

A focused application layer.

Go is a compiled language with built-in concurrency tools. It is a strong fit for network services and APIs—the work that connects an interface to the business behind it.

POSTGRESQL / TRUSTWORTHY DATA

Relationships that hold together.

PostgreSQL provides relational data, transactions, and integrity constraints. That matters when customers, permissions, orders, and content need consistent relationships.

SERVERLESS / CAPACITY WITH PURPOSE

Scale the parts that need it.

The goal is to use managed infrastructure, caching, and background processing to respond to demand. Real capacity depends on workload, database design, provider limits, and testing.

Underlying technologies: Go documentation ↗ · About PostgreSQL ↗

MIGRATION / KEEP WHAT MATTERS

Move the business.
Preserve its meaning.

A migration is more than copying pages. The important work is understanding what each record means and how the destination should use it.

01

Content & discovery

Pages, posts, structured fields, media, metadata, slugs, and redirects. Preserve the way people find and understand your work.

Builder · Docs · Media · Search · SEO

02

People & access

Accounts, ownership, roles, permissions, and customer relationships. Identity mapping and authentication need an explicit plan.

Auth · CRM · Forms · Community · Chat

03

Business & history

Orders, memberships, support records, referrals, and activity. Historical records and live financial or reward effects must be handled separately.

Commerce integrations · Support · Affiliate · Roadmap

WordPress ↔ EmDash ↔ Winkdom is the direction.

Support varies by product, data type, destination, and migration direction. A supported export does not imply full-site migration or automatic return. Confirm coverage before planning a live move.

  1. 01 / DISCOVER

    Map the site.

    Identify content, plugins, integrations, and the workflows your business depends on.

  2. 02 / PREPARE

    Agree the scope.

    Confirm supported data, destination behavior, ownership mapping, and a recovery plan.

  3. 03 / REHEARSE

    Review a copy.

    Check content, relationships, permissions, links, and key journeys in an isolated destination.

  4. 04 / TRANSITION

    Move with intent.

    Plan the final synchronization, domain changes, monitoring, and the conditions for rollback.

CLOUD WORKFLOWS / WORDPRESS WITH INSTAWP

Less repetition.
More momentum.

InstaWP is the main cloud platform in our WordPress direction. Its staging environments provide a separate copy where changes can be reviewed before moving to the live site.

The Winkdom automation vision connects site creation, configuration, content delivery, and ongoing operations through supported APIs and controlled workflows. Explore the Sites creation journey.

Available actions depend on the provider, plan, product, and configured connection. End-to-end public AI launch remains a developing workflow.

How InstaWP staging works

A CLEAR PATH FROM IDEA TO OPERATION

01Create & configureA suitable foundation for the project.
02Preview & refineReview content and behavior before release.
03Connect & operateSupported integrations, deliberate access, ongoing care.

Workflow concept · Availability differs by integration.

THE STANDARD ACROSS EVERY PLATFORM

Speed. Quality. Security.
Designed together.

Fast where it counts.

Reduce unnecessary work, cache deliberately, and measure the journeys people actually use.

Consistent in the details.

Preserve readable interfaces, light and dark appearances, accessibility, and useful recovery states.

Access with a purpose.

Use server-side authorization, scoped connections, protected credentials, and tested recovery procedures.

AN OPEN FOUNDATION / A CONNECTED BUSINESS

Built to share.
Supported to grow.

We plan for winkdom.org to become the home of the open-source CMS and free plugin editions: a place for source, documentation, and community participation.

Winkdom.com is the home for the wider product and business experience. Edition details, licensing, downloads, and managed services will be explained product by product.

The .org site and its public distribution catalogue are planned. Free software and paid hosting or services are separate parts of the picture.

BUILD YOUR KINGDOM. IN A WINK.

What comes next
for your business?

Tell us your current platform, the tools you rely on, and what you want to build next. We can start with the right questions and a realistic path.

Secure account access

Welcome back

Sign in to continue without leaving this site.