Neocortex

Neocortex Build

Build apps that become part of the enterprise brain.

Use the same App SDK, platform services, design system, permissions and AI capabilities that power Neocortex. Build internally, privately for a client, or submit a commercial app to the Marketplace.

The developer model

Small app surface. Big platform capability.

You own the domain-specific experience. Neocortex provides identity, organisations, permissions, documents, search, AI routing, agents, jobs, notifications, audit and the shared design language.

App SDK

Typed manifest, routes, lifecycle, scopes and shared UI primitives.

Platform APIs

Reuse governed data, documents, AI, jobs, connections and audit instead of rebuilding them.

Security by default

Least-privilege scopes, user permissions, tenant isolation and auditable actions.

Marketplace ready

Version, test, submit, review, publish and update without coupling the app to the core.

Quickstart

From zero to a working app in minutes.

  1. 01

    Start from the starter

    Copy the Neocortex Starter App or scaffold a new package with the App SDK.

  2. 02

    Declare the contract

    Define identity, version, category, routes, scopes, permissions, settings and installation rules.

  3. 03

    Build the experience

    Use the shared components and platform services. Keep secrets and privileged work server-side.

  4. 04

    Test the lifecycle

    Install, configure, exercise permissions, uninstall and upgrade with synthetic data before submission.

  5. 05

    Submit

    Create a Marketplace package, provide evidence and changelog, then send it through review.

apps/sample-crm/manifest.ts
export default defineApp({
  id: 'sample-crm',
  name: 'Sample CRM',
  version: '1.0.0',
  category: 'business',
  routePrefixes: ['/sample-crm'],
  scopes: ['orgs', 'documents', 'ai-router', 'audit'],
  permissions: ['crm.read', 'crm.write'],
  maturity: 'preview',
})
npm run dev
npm run lint
npm run build

Sample App

Learn by copying a real pattern.

The Starter App is the canonical reference for route ownership, app registration, shared UI, settings, permissions, AI actions, audit events and Marketplace metadata. Use it as the smallest safe starting point rather than inventing a parallel architecture.

Manifest

Identity, versioning, category, route prefixes, dependencies, scopes and installation defaults.

UI + routes

A focused app shell with responsive pages, loading/error states, empty states and accessible controls.

Platform integration

Server-side calls to governed platform services with the signed-in user and organisation context preserved.

Marketplace submission

A clear path from private build to trusted Marketplace app.

01

Prepare

Package the app, README, screenshots, manifest and support contact.

02

Security

Document scopes, data flows, external services, secrets and AI behaviour.

03

Quality

Provide install/upgrade/uninstall tests and verify responsive accessibility.

04

Submit

Send the package, version, changelog, evidence and requested Marketplace listing data.

05

Review & publish

Neocortex validates the contract, security, UX and lifecycle before publication.

Submission checklist

  • Manifest and semantic version
  • Screenshots / product demo
  • Permissions and data-flow declaration
  • External dependency disclosure
  • Security and privacy notes
  • Install / upgrade / uninstall tests
  • Accessibility and mobile checks
  • Changelog and support owner

What good looks like

Build for the brain, not beside it.

Composable

Use platform services and contracts. Avoid duplicate identity, permissions, storage or AI routing.

Observable

Emit useful audit and operational signals. Make failures diagnosable without exposing sensitive content.

Removable

An app must be installable and uninstallable independently, with clear data retention behaviour.