Platform

Structure is metadata. Behavior is C#.

Two primitives, cleanly separated. Everything you build in Cosmic XRM is one or the other — which is why the whole platform stays understandable.

Metadata

Model the business, get an app

Entities, fields, relationships, forms, lists, and security roles are data, not code. Author them in the admin app and the runtime renders them immediately.

Admin — entity designer
Cosmic XRM admin app showing the Account entity definition with appearance, features, and display settings
The Account entity in the admin app: appearance, features, and display settings are all metadata.

Entities & fields

Define your domain objects with typed fields — text, numbers, dates, options, lookups, and polymorphic references across entity types.

Relationships

One-to-many, many-to-many, and one-to-one relationships with usage tracking, so the model stays navigable as it grows.

Forms & lists

Layouts are metadata too. Default forms and lists generate from the model; refine them in the designer when you want control.

Plugins

Real code, real tooling

Behavior lives in C# plugins built against a typed SDK: server plugins for data logic, form plugins for UI behavior, action plugins for commands. Test them with your normal test stack, review them in normal pull requests, version them like the software they are.

There is no JavaScript layer and no low-code workflow builder to outgrow. If you can express it in C#, your CRM can do it.

RenewalFormPlugin.cs
public class RenewalFormPlugin : IFormPlugin
{
    public Task OnFieldChangedAsync(
        IFormExecutionContext form)
    {
        if (form.GetValue<decimal>("value") > 50_000m)
        {
            form.SetRequired("approver", true);
        }
        return Task.CompletedTask;
    }
}

Designer & runtime

Design visually, render generatively

The designer is a drag-and-drop canvas over your real metadata — forms, lists, and parameterized composite components with typed inputs and C# script behavior. The end-user app renders everything from the same definitions, so what you design is exactly what ships.

End-user app — generated workspace
Cosmic XRM end-user app home with chat assistant, entity navigation, and quick actions
The end-user app: navigation, lists, and quick actions appear as soon as the metadata exists.

Canvas designer

Tabs, sections, fields, actions, and platform components composed visually, with live preview seeded from representative data.

Composite components

Build reusable components with a typed input/output contract and C# script behavior — your design system, not ours.

Generative UI

Every entity gets forms, lists, search, and activity timelines out of the box. No hand-built pages to maintain.

See it running in your subscription

From marketplace install to first custom entity in an afternoon.