Use case: developers

Build on WordPress primitives instead of a fragile embed.

WordPress developers can use native Episode posts, taxonomies, templates, archive routes, Query Loops, and blocks while Kleis manages the supported Planning Center connection.

See pricing Review product facts

Typical workflow

Kleis proxies read-only supported API requests through its service, stores encrypted OAuth tokens outside WordPress, synchronizes sermon entities, and exposes event data to dynamic blocks. The developer owns theme integration and public presentation.

Product boundary

Kleis is not a general Planning Center SDK. API proxying is limited to supported Publishing and Calendar read paths, and third-party builder compatibility must be tested for the project.

Explore the product

Sermon syncPlanning Center Publishing in WordPress. Event displaysPlanning Center Calendar blocks. Compare approachesManual entry, embeds, custom development, and Kleis. Read the docsInstallation, setup, design, and maintenance.

Connect Planning Center to WordPress with Kleis.

Use the content your team already maintains, then control the public design with WordPress.

Choose a plan Contact support