Codeweber

Platform-operator governance for abuse-protection rate limits: declared policies, bounded overrides, provenance-aware enforcement, reset and erasure.

Configurable admin dashboard with module-provided widgets.

User accounts, sessions, roles and password resets.

Multi-tenant directory with tenants and organizations.

Polymorphic activities, notes and comments foundation for all modules.

Polymorphic notes — attach free-form notes to any entity.

Polymorphic hierarchical comments — attach threaded discussions to any entity.

Universal stage pipelines for any entity — polymorphic subject, stage history with time-in-stage, per-owner bindings.

Core CRM capabilities for people, companies, deals, and activities.

Counterparties (clients, suppliers, partners) — extends customers with party roles and country-aware requisites.

Enrich Russian counterparties from the EGRUL/EGRIP + bank registry by ИНН/ОГРН/БИК, with ФИО and address autocomplete. Credential-only provider consumed by the counterparties module.

Legally-significant electronic document exchange (ЭДО) with counterparties via the Kontur.Diadoc operator: invite counterparties, sign documents, send and receive signed documents into the database.

Warehouse topology, item inventory profiles, lot/serial tracking, balances, reservations and an append-only movement ledger. Phase 1 (Core Inventory) — no receiving/putaway/picking yet.

Shared persistence for DataTable perspectives (columns, filters, saved views).

User-defined entities, custom fields, and dynamic records storage.

Shared configuration storage and helpers for module settings.

System-wide forward proxy for outbound AI/Telegram traffic from restricted regions.

Admin-configurable app-cache Redis connection: live switch without restart, connection test, epoch-based cache reset.

Thin API host for the shared variables engine (CP-189): the picker tree and the resolve/preview endpoint over {{entity.field}} tokens. Owns no tables; modules declare sources via variables.ts + a DI resolver service.

Flat text templates (email / SMS / chat / notification / push) authored with {{entity.field}} tokens and rendered through the variables engine (CP-190). Stores and resolves templates; delivery stays with channel owners.

Document constructor (CP-191): Aspro-style 3-tier model (document type → template → document) over the shared ProseMirror editor, {{entity.field}} variables through the variables engine, DOCX/PDF render into attachments.

Document repository (CP-192): the company-wide document repository — spaces, nested folders, documents, append-only versions, capped-inheritance permissions, record links (pin/follow), labels, retention classification and a dedicated view/download access ledger — built strictly as a management layer over the shared attachments blob storage.

Hybrid query layer with full-text and vector search capabilities.

Tracks user actions and data accesses with undo support scaffolding.

Continuous production security checks — RBAC-grant drift detection, tenant-isolation spot-checks, and synthetic-tenant probing. See .ai/specs/CP-201-2026-07-11-security-audit-coverage.md.

File attachments and media management.

Configurable catalog for products, variants, and pricing used by the sales module.

Quoting, ordering, fulfillment, and billing capabilities built on modular pricing and tax pipelines.

Manage access tokens for external API access.

Organization-scoped dictionaries for reusable enumerations and appearance presets.

Static informational pages such as terms of service and privacy policy.

Self-service tenant and organization onboarding flow.

Auto-generated documentation for all HTTP endpoints.

In-admin, read-only documentation aggregated from each enabled module (CP-180).

Declarative in-context interface guidance: per-module hint banners with a per-user visibility toggle (CP-231).

Business Rules Engine for defining, managing, and executing business logic and automation rules.

Global feature flags with tenant-level overrides.

Orchestrate business processes with state machines, transitions, and activities

Unified search module with pluggable strategies (Meilisearch, Vector, Tokens).

Currencies and Exchange rate management

Availability schedules, rulesets, and shared planning rules.

Assets and resources with scheduling policies.

Teams, roles, and employee rosters.

Bookable services, appointments, and the shared booking calendar (CP-237).

Working groups (Команды) — foundation grouping with role-on-membership.

CP-093 Layer 3 — point-in-record access grants (user/department/team), reusable across any record type.

CP-318 — one library of named saved views shared by every surface (tables, sidebar, boards, cards, pipeline templates).

Event bus and subscriber dispatch

In-app notifications with module-extensible types and actions.

Generic server-side progress tracking for long-running operations

Core integration framework — external ID mapping, status badges, and integration registry.

Streaming data sync hub for import/export integrations.

File-upload-based CSV import foundation built on top of the data sync hub.

Internal messaging system with attachments, actions, and email forwarding.

Unified hub bridging external chat/email channels (Slack, WhatsApp, Email) to the Messages module. Adapter contract, channel-native payload storage, reactions, and per-channel threading.

MCP server for AI assistant integration with multi-tenant support.

System-wide entity translation storage and locale overlay for CRUD responses.

Database-managed scheduled jobs with admin UI

Receives forwarded emails via webhook, extracts structured action proposals using LLM, and presents them for human-in-the-loop approval.

Payment gateway adapter contract, registry, transaction tracking, and webhook routing.

Pay links, checkout templates, public payment pages, and checkout transaction tracking.

Accept card payments, Apple Pay, Google Pay, and bank transfers via Stripe.

Connect personal mailboxes via IMAP for inbound polling and SMTP for outbound delivery. Pairs with the Communications Hub (SPEC-045d).

Connect per-user Gmail accounts via OAuth2. Outbound via gmail.users.messages.send; inbound via History API polling. Pairs with the Communications Hub.

Connect per-user Yandex Mail accounts via OAuth2. Auth uses Yandex OAuth; transport is IMAP/SMTP authenticated with XOAUTH2 using the OAuth access token. Inbound via UID-based IMAP polling; pairs with the Communications Hub.

Connect per-user Mail.ru mailboxes (@mail.ru, @bk.ru, @inbox.ru, @list.ru) via OAuth2. Transport is IMAP/SMTP authenticated with XOAUTH2 using the OAuth access token. Inbound via UID-based IMAP polling; pairs with the Communications Hub.

Provision and manage employee mailboxes on the company domain via the Yandex 360 Directory API. Pairs with the Yandex email channel for auto-connect.

Import Akeneo PIM categories, product attributes, and products into the Open Mercato catalog.

Shipping carrier adapter hub with rates, shipment creation, tracking, and webhooks.

Standard Webhooks compliant outbound webhook delivery for platform events.

Interactive entity-model explorer (cards + relations + filters)

Unified chat shell for internal team messaging and external client conversations.

Customer-facing authentication with two-tier identity model and full RBAC.

Self-service customer portal framework with login, signup, dashboard, sidebar navigation, and extensible widget system.

Voice and video calls via LiveKit SFU with call journal and participant tracking.

Store attachments and files in AWS S3, DigitalOcean Spaces, MinIO, or any S3-compatible object storage.