Docs
Clikkle Core technical docs

Docs_

Build secure and scalable applications on Clikkle Core. Learn the platform, configure project resources, use SDKs and APIs, and move from first setup to production with customer-verified guidance.

Next.jsReactVueAngularSvelteReact NativeFlutteriOSAndroidKotlinSwiftNode.jsPythonPHPRuby.NETGoDenoDart

Show me some code

If you learn best by doing, follow a supported workflow built from the same customer path Clikkle tests.

Explore capabilities

Core services, developer tools and operating contracts in one documentation system. Deep documentation is released as each real customer contract is verified.

Build faster with AI

AI belongs beside the developer workflow without inventing authority that does not exist in the owning service.

Theo developer workflowsAI-assisted developer guidance is published as the corresponding Core contracts are verified.Documentation track
MCP integrationsModel Context Protocol guidance will live here when the public Clikkle MCP contract is certified.Documentation track
IDE integrationsEditor and agent integrations are documented against released SDK/API capabilities, not speculative behavior.Documentation track
AutomationAutomation examples will connect to Q7 Logic and Core APIs through explicit versioned contracts.Documentation track

Explore ways to integrate

Choose the interface that matches your application. SDK, REST, package and reference guidance all remain anchored to the same owning Core contracts.

Need product help?

Clikkle Help covers account access, billing, organization and product-operation questions. Technical implementation stays here in Docs.

Migrate to Clikkle

Migration guidance belongs in the documentation platform as each destination service reaches a verifiable customer path.

MongoDB → Morph DBMigration planning, compatibility evidence, synchronization and controlled cutover are part of the Morph DB roadmap.
Existing package registriesMove package release workflows to G7 Packages using repository-scoped credentials and immutable versions.
Identity workloadsAuth migration guidance will publish only after the production Auth customer contract is certified.
Application hostingSites migration guidance is reserved for the Sites commercial build that follows Auth and Analytics readiness.