K k0smos
Home Documentation Sign in
en it

Private framework - multi-tenant - modular

Tailored digital ecosystems

k0smos is a PHP application base for tenant-aware products: runtime modules, an operational back office, APIs and AI integrations in a maintainable architecture.

Open back officeDiscuss the project

A solid base for tenant-aware products

k0smos puts real operational capability first: solid architecture, composable modules and management tools — no fluff.

TN

Tenant-aware architecture

Configuration, database, theme and modules stay isolated per tenant, with hostname-based resolution.

ERP

Operational ERP

Clients, projects, tasks, documents and deadlines share one coherent workspace.

MD

Runtime modules

Each tenant enables only the needed capabilities while routes, services, menus and permissions share one contract.

MOD

Modular by design

Each organization enables what it needs today and adds new areas as its work evolves.

BO

Operational back office

Users, roles, content, media, widgets, menus and theme preferences live in one administration panel.

AI

AI where it matters

Assistance, review and automation support people through repetitive steps and informed decisions.

API

APIs and security

Personal tokens, ACL, voter policies, protected routes and granular permissions keep access and capabilities separated.

CM

Content and media

Info pages, blog, shop, widgets and public or private assets can be managed without editing templates.

AI

AI and automation

LLM providers, revisions, async jobs and queues integrate automation while preserving operational control.

From domain to operational product

The value is in the process: start from real constraints, then compose modules and integrations through verifiable steps.

1

Domain analysis

We map workflows, roles, data and constraints before choosing modules or integrations.

1

Understand

We clarify goals, responsibilities, data and the steps that slow work down today.

2

Module composition

We enable only what the tenant needs and add extensions where the domain requires them.

2

Compose

We bring the necessary capabilities into simple workflows for the right people.

3

Controlled evolution

Migrations, fixtures, documentation and runbooks keep the project manageable over time.

3

Evolve

We add new capabilities without losing control, operational continuity or project knowledge.

Modules as application contracts

Each area carries its own routes, services, menus, permissions, migrations and technical documentation.

InfoInstitutional and legal pages
ClientsRecords, relationships and history
WidgetEditable HTML blocks
ProjectsTasks, ownership and progress
MediaPublic and private assets
SalesCatalog, orders and documents
BlogEditorial content
SupportRequests, tickets and priorities
E-commerceCatalog, cart and checkout
PlanningCalendar, deadlines and reminders
TicketTasks and operational back office
ContentPages, media and communications
CalendarEvents and planning
ControlRoles, access and notifications
AILLMs, revisions and workers

For project operators

  • Tenant configuration and theme preferences
  • Users, roles, permissions and enabled modules
  • Content, widgets, menus and media managed from the panel
  • Operational workflows with tickets, calendar and notifications
  • Clear information on AI, providers and automation

For organizational leaders

  • A coherent view of people, work and priorities
  • Roles and access aligned with real responsibilities
  • New capabilities without redesigning the whole system
  • Processes that are easier to read, verify and improve

For developers and maintainers

  • Isolated modules with their own services, routes and migrations
  • Conservative fixtures that do not overwrite editable content
  • Separate Plates templates and theme assets
  • CLI, queues and job handlers for repeatable operations
  • AI.*.md and module README documentation

For people working every day

  • Information and tools gathered in one environment
  • Tasks, deadlines and communications kept in context
  • Fewer repetitive steps through focused automation
  • An experience that adapts to each role and workflow

Do you need to consolidate a product or digitize a workflow?

Start from the domain and build incrementally: first the operational core, then modules, integrations and automation.

Open back officeDiscuss the project