Questions people actually ask.

A production-ready headless core — a complete back end that handles business logic, data, security, and integrations, exposed as a documented API. It comes in three parts: the Core (the engine), Quarkino Admin (the panel your team uses), and the front end, which you design and build yourself.

It includes a content engine capable of modelling any content shape, so it does what a CMS does. But it also handles commerce, cases, memberships, notifications, and reporting. Calling it a CMS undersells about two-thirds of it.

Yes — it's the core our own studio's client work runs on. Every rough edge gets found by us first, on our own deadline. That's the main reason it's in the state it's in.

Yes. Book a demo and we'll walk through it against your actual requirements rather than giving a generic tour.

TypeScript, Fastify, PostgreSQL, Prisma, BullMQ on Redis, and S3-compatible storage. Documentation is OpenAPI, generated from the code.

Any. Headless means the back end makes no assumptions about the front end. Next.js, a native mobile app, several clients at once — all against the same API.

Yes. Quarkino runs on standard infrastructure and can be deployed to your own environment.

Through a registry — the formal extension point for field types, payment gateways, discount rules, notification channels, dashboard widgets, reports, and importers. You register a definition rather than editing core code, which is why upgrades stay routine.

It disappears. Its API routes return 404, and it's removed from the admin menu, from search, from bulk actions, and from the dashboard. Not hidden — absent.

Yes, and adding one requires no code change. System text comes from keyed catalogues; content is modelled once with per-language siblings. Machine translation produces drafts a human approves, and translation coverage is tracked.

Either. Most of our work is building the whole product. Some clients license the core and build with their own team.

Six weeks is typical for a real, live product with accounts, data, and security. The page on it breaks down where those weeks actually go.

A decision-maker who's available, content or a plan for content, and willingness to cut scope early. Content is the most common cause of delay, and it's never an engineering problem.

Documentation and a handover session with whoever will operate it. Ongoing support is available and priced separately. Core updates reach your project either way.

Hashed with argon2id. Never in plain text, at any point.

Nowhere near Quarkino. Payment happens on the gateway's own secure page. There's no code path where a card number could be stored, because it's never received.

Quarkino provides full personal data export and erasure, with an explicit, code-enforced line between what may be deleted and what must legally be retained. Compliance also depends on how you operate it — we'll walk through it properly.

Yes. Every sensitive operation is recorded with actor, timestamp, and detail, with field-level history on records that need it.

There's a dedicated channel and we respond to every report.

No. Quarkino is deployed and configured for a project rather than signed up for, so a trial wouldn't show you anything useful.

Priced per project, because the honest variable is how much of your brief falls outside what already exists.

Your data is yours and exports in standard formats. We don't build in exit friction.

No. What you switch on depends on what your product needs, not what you paid.