AI in ELWIS

Build with AI,
enhance with no-code.

Describe the app you need in plain words. Your AI plans it, ELWIS builds it within your permissions, after your Confirm.

A CRM for customers and their orders

Your model: Claude ChatGPT Astra Local model
Runs on your own API key
BOOK DEMO

Describe it. ELWIS builds it.

Five steps from a sentence to a working app. Step three is always yours.

Phase 1 · Data model 3 record types · 2 links Confirm
01

You describe

Say what the app should do: in a chat, from your terminal, or out loud.

02

AI plans

Claude or OpenAI drafts the data model, pages and menu, on your own key.

03

You confirm

Each phase arrives as a card. Nothing runs until you click Confirm.

04

ELWIS builds

ELWIS tools make every change, inside your roles and permissions.

05

App is live

Sample data in, menu ready, first screen open. Ready to demo.

The model only plans. ELWIS tools make every change, with your permissions, after your Confirm.

Two ELWIS MCPs

Builds the app.
Works the data.

Your AI talks to ELWIS through two MCP servers. Builder MCP shapes the application; Data MCP works inside it. Both run within your permissions.

YOUR AI Claude ChatGPT Astra Local model

Builder MCP

Shapes the application.

Create applicationData modelLinksPagesMenusWorkflowBranded page

Data MCP

Works inside it.

Create work itemImport dataCreate invoiceChange statusRead & report
ELWIS app window: Orders page with Open 12, Invoiced 38, Overdue 2 and three orders marked Sent, Paid and Draft
You decide

Three phases. Three Confirms.

Builder MCP works in phases. Each phase arrives as a card, and nothing is built until you Confirm it.

Phase 1 of 3 · Data model3 record types, 1 link, dropdowns, sample data
Built 09:41
Phase 2 of 3 · PagesDashboard, a table per record type, forms
Built 09:43
Phase 3 of 3

Menu

Waiting for you
What ELWIS will build
Header menuon every page
Homelinked first
Customers · Ordersone link per table
Nothing runs until you click Confirm. Edit plan CONFIRM
App is live after your Confirm

Not a mock-up. A working app.

Builder MCP creates real ELWIS objects. Colours, icons and links included, without one click in a setup screen.

Data model

Record types, fields and links, from one sentence. Validation and select options included.

Record types
Fields
Links
ELWIS record type editor for Customers with fields Name, E-mail, Status, Orders and Owner. Select options New, Active and Churned are open.ELWIS record type editor for Customers with fields Name, E-mail, Status, Orders and Owner. Select options New, Active and Churned are open.

Pages & dashboards

Tables with filters, detail pages with forms, dashboards with real widgets.

Dashboards
Tables
Detail pages
ELWIS sales dashboard with open orders, revenue, overdue and customer widgets and a chart of orders per month.ELWIS sales dashboard with open orders, revenue, overdue and customer widgets and a chart of orders per month.

Menus & branded pages

A navigation that makes sense, with your logo and colours on the public page.

Menus
Branded pages
Branded patient portal for Dent Clinic with a side menu and three bookable appointment slots.Branded patient portal for Dent Clinic with a side menu and three bookable appointment slots.

Sample data & repairs

Demo data to click through right away, and fixes when something is off.

Sample data
Repairs
ELWIS Orders table filled with 38 sample orders generated by Builder MCP. Repair chat: the hidden status column was found and a fix is ready for your Confirm.ELWIS Orders table filled with 38 sample orders generated by Builder MCP. Repair chat: the hidden status column was found and a fix is ready for your Confirm.
Claude with Data MCP connected, previewing a new invoice for order 1042 and a status change, waiting for Confirm
ELWIS invoices table with the new invoice INV-2026-118 added by Claude via Data MCP and confirmed by you
Data MCP

AI inside your
processes.

Any assistant your team already uses can work with your records: read, add, edit. A work item, an invoice, a status change, an import. Within your permissions, after your Confirm.

Create work itemCreate invoiceChange statusImport dataRead & report

The assistant sees and changes only what you may.

Ask once. Watch it appear.

Pick the way that fits your team. Same two MCPs, same permissions, same Confirm.

Browser chat connected to ELWIS: Codex plans a CRM, phase 1 confirmed, phase 2 Pages waiting for your Confirm
Your AI assistant · connected to ELWIS

Build a CRM for customers and their orders.

Plan ready: 3 record types, 1 link, 3 pages and 1 menu. I build it phase by phase.

elwis-builder MCP

Phase 1 · Data model confirmed · 12 customers, 38 orders

Phase 2 of 3 · Pages

Dashboard, a table per record type, forms to open and edit records.

Waiting for youConfirm
elwis-builder · elwis-data MCP
n8n workflow: new order e-mail, AI agent, ELWIS Data MCP and notify sales, last run succeeded
n8n · New order e-mail → ELWIS

New order e-mail

Trigger · shared inbox

AI agent

Reads the order, finds the customer

ELWIS Data MCP

create_record · Orders

Notify sales

Message to the team

Last run · 09:41

Succeeded

Order #1042 read from the e-mail

Customer Nordline s.r.o. matched

Order created in ELWIS through Data MCP

n8n · elwis-data MCP
Claude Code terminal building a CRM through the elwis-builder MCP, waiting for your Confirm between phases
Claude CodeCodexCursor
$ claude "Build a CRM for customers and their orders"

› elwis-builder MCP · build_application  name: "CRM"
› plan · 3 record types · 1 link · 3 pages · 1 menu

› phase 1 · Data model     card ready
  waiting for your Confirm …
✓ confirmed by you · 09:41
› build_artifact_type  Customers ✓  Orders ✓  Contacts ✓
› build_link  Customer → Orders (1 : n) ✓
› sample_data  12 customers · 38 orders ✓

› phase 2 · Pages          card ready
  waiting for your Confirm …
elwis-builder · elwis-data MCP
ELWIS assistant inside the Orders page proposing a Priority field, shown as a preview until you Confirm
Pages / OrdersPreview

ELWIS assistant

Soon

Add a Priority field to Orders: High, Normal, Low.

Change · Orders

Field “Priority”, dropdown

Options High · Normal · Low

Column in the Orders table

EditConfirm

Preview of the change · not built yet

#1044Steelform GmbHHigh
#1043Kovex TradeNormal

You stay in control.

Nothing happens until you click Confirm. Every phase, every repair, every record: a card first.

Phase 1 · Data model · 3 record types Confirm

Your permissions apply

The assistant sees and changes only what you may. Same roles, same rights as the person asking.

Same roles as your users.

Your own AI account

Connect a Claude or OpenAI key once. Your usage, your billing, your data agreement.

Your key, your bill.

Open by design

Bring the AI you already use.

Three parts. You own two of them, and the bridge is an open standard.

YOUR AI

Any model

Public AI

Start in minutes with the assistant your team already uses.

ChatGPTCodexClaudeAstra
Local LLMAdvanced

Run a model on your own servers. Your data never leaves your network.

THE BRIDGE · OPEN MCP

Two ELWIS MCPs

Builder MCP builds the app: types, fields, links, pages, menus.

Data MCP works with your records: read, add, edit.

An open standard. No proprietary plugin, no vendor SDK.

YOUR PLATFORM

ELWIS

Your data: one source for every model

Your permissions: AI sees only what you may

Your Confirm: no change without your click

The same ELWIS you already run.

No lock-inSwitch models, keep your apps.
Keep it in-houseAdvanced: run a local model on your servers.
Your own AI accountConnect a Claude or OpenAI key once.
ROADMAP

Where it
stands today

Terminal and n8n are live. The chat inside ELWIS is next.

  1. Available today
    Terminal (Claude Code, Codex)n8n automationsVoice in, voice out
  2. In progress
    Chat inside ELWIS

    Soon: just ask in the chat.Type or talk, review on a card, Confirm.

  3. Coming soon
    Internal agents

Ready to try AI in your process? Prepare for your demo.

Bring one real process. Leave with a plan for a working app, built with your AI, your permissions and your Confirm.