Core Apps

oikapi ships a curated catalog of first-party business suites you can install on any instance. These are maintained by the oikapi team, distributed under the @oikapi/ namespace, and cover common CRM, ITSM/CMDB, finance, and operations workflows. Each suite is a standard app — once installed, it’s fully customizable like any app you build yourself.

First-party suites

Suite	Description
CRM	Leads, opportunity pipeline, and activities.
Sales	Quote-to-cash — quotes, orders, invoices, payments, and subscriptions.
IT Service Management	Incidents, changes, problems, and a service catalog on the CMDB spine, with business-calendar SLAs.
CMDB	Configuration management database — typed configuration items, a dependency graph, and discovery-fed reconciliation.
Inventory	Warehouse and stock management — products, stock levels, movements, and physical counts.
HR Core	The HR employment spine — employees, departments, the org-chart graph, leave, attendance, and compensation.
Purchasing	Vendor management, purchase orders, goods receipts, and vendor bills.
Projects	Project delivery spine — projects, work items, a containment hierarchy and blocking dependency graph, milestones, and time tracking.
Accounting Integrations	Receives GL posting entries from operational suites and syncs them to an external accounting system.
Event Management	AIOps basics — ingest monitoring events, deduplicate into alerts, correlate, bind to configuration items, and auto-raise ITSM incidents.
Discovery	A scheduled, sync-ingest-fed refresh of CMDB configuration items and their relationships from a source.

Note

The first-party catalog is evolving. Suites are added, refined, and occasionally retired as the platform matures, so the set above reflects the current catalog rather than a fixed roster.

How suites relate

Suites are independent apps — none hard-requires another to install. Where one suite enriches another, it declares a cross-app access request rather than a hard dependency. For example, ITSM reads CMDB configuration items to link incidents to affected services, and Event Management binds alerts to CMDB items and raises ITSM incidents. Cross-app access requests are reviewed and approved during install, so you stay in control of which suite can read which tables.

See Applications for how app segregation and cross-app access work.

Installing apps

# Install a first-party suite from the marketplace (latest version)
oi app install @oikapi/crm

# Install a specific version
oi app install @oikapi/crm@1.2.0

# Fork a suite as a customizable template under a new name
oi app install @oikapi/projects_core --as my-projects

You can also install from a local directory or a built .oikapp file:

oi app install ./my-app                 # build + install from a source directory
oi app install ./my-app-1.0.0.oikapp    # install a built package

Note

Installing from the marketplace requires your instance to be connected to the central registry. See Installing Apps for details.

What’s included

Each suite provides:

• Tables and fields – the data model, with appropriate field types and references
• Roles and permissions – roles tailored to the suite’s workflow, with default grants
• Views, forms, and business rules – list views, form layouts, and the automation that drives the workflow
• Demo data – optional sample records for evaluation, managed separately so it can be cleanly removed

Demo data bundled with a suite is managed with oi app demo (list it, or remove it without touching real records).

Customization

An installed suite is a starting point. After installation you can:

• Add fields to existing tables
• Create additional tables that reference the suite’s tables
• Modify permissions and roles
• Add or edit business rules
• Build custom web interfaces