Skip to content
all products

A MaxICo Labs product

Pult — a CMS for sites

One panel for sites and online stores

Product in detail

How this product works.

A component-based CMS foundation for websites and online stores, adapted to each project. Content, catalogue, orders, SEO and analytics are included only where required.

Pult is MaxICo's internal CMS foundation for projects where an off-the-shelf admin panel does not fit the content or commerce logic. Sections are selected from the information architecture of the specific site.

Next.js, SEO structure, language versions, analytics, catalogue, cart, payments and feeds are not treated as one automatically included bundle. Each part is designed and tested according to scope.

Code rights, data access, hosting and support scope are documented in the agreement. Extensions are estimated as separate changes rather than promised without limit.

Cover of the Pult CMS interface prototype

Interface prototype

Pult CMS with demonstration data.

The archive and navigable demo show the dashboard, orders, stock, leads, analytics, and content. They do not prove a production backend, payments, or live integrations.

Inspect the Pult archive

Key parts

What's inside this product.

A component-based CMS foundation for websites and online stores, adapted to each project. Content, catalogue, orders, SEO and analytics are included only where required.

Pult — a CMS for sitesInternal foundation
01

A modular panel for the specific project's structure

Pult is MaxICo's internal CMS foundation for projects where an off-the-shelf admin panel does not fit the content or commerce logic. Sections are selected from the information architecture of the specific site.

02

SEO, languages and analytics within the agreed scope

Next.js, SEO structure, language versions, analytics, catalogue, cart, payments and feeds are not treated as one automatically included bundle. Each part is designed and tested according to scope.

03

Commerce modules after payment and accounting requirements are checked

Code rights, data access, hosting and support scope are documented in the agreement. Extensions are estimated as separate changes rather than promised without limit.

Before implementation

We first map the product to your workflow.

The introductory call gathers context. The available foundation, integrations, and ballpark scope are confirmed only after a separate review of requirements and dependencies.