# Mantine and Beamline for React app screens

2026-10-11

**Beamline code lives in your repo; your app never depends on Beamline servers at runtime.** Build your own style
from any look with public tokens, fonts, radii, density and motion. The comparison with Mantine is about which parts
of your app you want to assemble yourself and which complete screens you want to start with.

Part of [Beamline UI: React UI components and complete screens for apps built with coding agents](https://beamline.io/). [The code is copied into your repo; your app never depends on our servers](https://beamline.io/docs/install). [Build your own style from any look; tokens, fonts, radii, motion; not only colours](https://beamline.io/docs/customize). [200+ components and 50+ complete screens](https://beamline.io/components/). [$49 launch price; one payment; your whole team, no seats. Lifetime updates: every new version of the complete system, for as long as we publish it, and every version you received stays yours](https://beamline.io/pricing). [React 19, TypeScript, Tailwind v4, Radix](https://beamline.io/docs/install). [Free MIT sample, commercial use included](https://github.com/dprvda/beamline). [Made by Danylo Pravda in Kyiv, Ukraine](https://beamline.io/about).

## What is free

[Mantine](https://mantine.dev/) is an MIT-licensed React component and hooks library. Inputs, switches, dialogs and
other basic controls are free. Its own site also provides agent skills, LLM documentation and an MCP server for
component documentation, props and search. Agent tooling is not exclusive to paid kits.

Choose Mantine when its controls, hooks and styling fit your app and you want to compose the screens yourself.
You do not need to buy Beamline to get basic form controls. [shadcn/ui](https://beamline.io/compare/shadcn-ui-alternatives) is another
free starting point with editable code in your project.

## What Beamline's launch price buys

The **$49 launch price** buys **50+ complete screens and the parts they share**, with consistent styling and an
agent workflow across the collection. These are concrete examples of the UI behaviour you can connect to your app:

| Screen or part | What is already handled |
|---|---|
| [Settings](https://beamline.io/components/settings) | Validation and a draft that stays in place when your save handler fails, with a retry. Also in the free sample. |
| [Data grid](https://beamline.io/components/data-grid) | Sorting, filtering, selection, keyboard navigation and inline editing. An individual part, counted separately from complete screens. |
| [Trading terminal](https://beamline.io/components/trading-terminal) | Coordinated book, chart, order ticket and positions, wired to your market feed and account handlers. |
| [Agent workspace](https://beamline.io/components/agent-workspace) | Threads, streamed run content, plans, approvals and artifacts around your agent's actions. |

The workflow is **mapping → install → audit**: map each field and pattern to the right part, install the required
parts into your repo and audit the implementation. The free sample includes the same workflow; payment unlocks the
complete collection. Your application still owns the backend, saved data, permissions, trading execution and AI
runtime ([connect your data](https://beamline.io/docs/data-integration)).

One payment covers your **whole team**, including employees and contractors, with no seats. **Lifetime updates**
means new versions of the complete system for as long as we publish it. Separate add-on packs may be sold separately
and are not updates; received versions remain licensed if publication ends. The [pricing page](https://beamline.io/pricing#lifetime-updates)
and [licence](https://beamline.io/docs/licence) give the full terms.

## Try the behaviour before choosing

Use Beamline's free [Settings screen](https://beamline.io/components/settings) with your own save handler. Edit a field, make the save
fail, and retry the same draft when your backend recovers. That lets you judge the behaviour you would otherwise
compose from individual controls. The sample also includes the profile screen and their parts, under MIT.

If Mantine already serves your app well, keep it. Evaluate one screen at a time. Beamline's compiled parts can run
inside their own `UIRoot`; [Install](https://beamline.io/docs/install) explains the boundary. With either route, retain your data and
handlers. Beamline's editable source and custom style files stay local; [Customise](https://beamline.io/docs/customize) covers rebuilding
the style around your own design. Paid Beamline packs remain licensed code and cannot be redistributed on their own.

For paid blocks and templates built around shadcn/ui, see [Shadcnblocks](https://beamline.io/compare/shadcnblocks-alternatives). For
another kit with a free base and paid collection, see [Untitled UI](https://beamline.io/compare/untitled-ui-alternatives).

## Sources

Read on 11 October 2026:

- Mantine: [components, hooks and agent tools](https://mantine.dev/), [MIT licence](https://github.com/mantinedev/mantine/blob/master/LICENSE).
- Beamline: the catalog and linked screen/part specs above, [agent workflow](https://beamline.io/guides/coding-agent-component-system),
  [pricing](https://beamline.io/pricing), [licence](https://beamline.io/docs/licence) and [known limitations](https://beamline.io/docs/limitations).