Skip to content

[ LUFF ENTERPRISE STUDIO · ENTERPRISE OS v4 ]

The Autonomous Software Factory & IT Division on Demand.

Luff Enterprise Studio designs, builds, launches and looks after the enterprise software your organisation runs on. Its Human Intelligence Brain builds most of it as ordinary code on your own machines and spends AI only where it matters, so your software arrives faster, costs less and is fully yours.

luff-enterprise-studio-latest.dmg · Apple silicon · macOS 13.0+

Typical delivery: 24 to 72 hours · 14-day trial in the app, no sign-up

Clinic records · milestone 3Illustration

Milestone gates · all 4

  1. 01BlueprintApproved
  2. 02DesignApproved
  3. 03BuildIn progress
  4. 04LaunchWaiting on Build

Next decision

Approve the test version when the build is done.

Activity tree

  • $[Delivery Manager] Luff Brain sent routine work to the Luff Engine
  • $[Database Architect] clinic records set up in the database
  • +[Web App Developer] Clinic records screen
  • r[Web App Developer] reading the approved clinic screens
  • w[Web App Developer] saving the clinic records feature
  • ✓[QA Analyst] each clinic sees only its own records · passed
  • +[Product Designer] Appointment booking screen
  • w[Product Designer] booking screen laid out in your theme
  • $[DevOps Engineer] new version live on the test copy
SYSTEM WORKING8 roles · web project
Illustration: milestone gates on the left, the crew activity tree on the right.

TWO PROBLEMS, ONE FIX

AI is used for everything. Software still takes months.

Luff solves both at once. At its core, the Luff Human Intelligence Brain joins an AI Architecture that keeps AI for the work that needs it, with a Software Architecture that builds the rest as ordinary code you own.

THE AI PROBLEM

AI is doing work that isn't AI work.

Most of what AI is asked to do in a software project is routine: the same screens, forms, database set-up and launch steps, written again for every project.

  • Routine work rewritten by AI, project after project
  • Hallucinations: made-up details that look right
  • Forgets your rules as sessions grow long
  • Results that change from one run to the next

THE SOFTWARE PROBLEM

Software is slow, costly and locks you in.

Agencies take months and bill for every change. No-code builders are quick, but you never own what you built. Either way, you depend on someone else.

  • Months of waiting before anything is live
  • A technical team you have to hire and manage
  • Scope that keeps growing, and bills with it
  • Code you cannot take with you
How Luff compares with a traditional agency and a no-code builder
Traditional agencyNo-code builderLuff
Time to deliver6 to 9 monthsWeeks, for simple prototypes24 to 72 hours, typically
Who owns the codeOften hard to get fully handed overNo export: you rent the platform100% yours, from day one
ScopeKeeps growing, billed by the hourLimited to what the builder allowsLocked at four decisions you approve
Cost$120,000 to $250,000+$500 to $3,000 a month, locked inFrom $49 a month, plus a $5 to $15 server

Agency and no-code figures are typical market ranges. Luff delivery times are typical and depend on the project.

HOW IT WORKS · THE LUFF HUMAN INTELLIGENCE BRAIN

Human judgement first. AI only when it is needed.

At the core of Luff sits the Luff Human Intelligence Brain. It holds two architectures together: an AI Architecture that solves the AI problem, and a Software Architecture that lets non-technical people build complex enterprise software.

SOLVES THE AI PROBLEMS

AI Architecture

  • Wasted AI usageRoutine work is done as ordinary code, so AI is used only where a job needs it.
  • HallucinationsEvery change is checked against your locked plan and the real code, so made-up details are caught.
  • Forgetting in long sessionsPlans and rules are saved to files, not held in a chat that forgets.
  • Mistakes that look rightAutomatic tests and checks run before any change goes in.
  • AI marking its own workWork is checked by separate roles and by code, never by the AI that wrote it.
  • Unstructured promptingFixed steps and four approval gates keep every job in order.

THE CORE ARCHITECTURE

Luff Human Intelligence Brain

Decides like an experienced engineer: does this job need AI at all, and who should do it?

SOLVES THE SOFTWARE PROBLEMS

Software Architecture

  • Needs technical skillsNon-technical people build complex enterprise software in plain words.
  • Months of waitingTypical delivery in 24 to 72 hours.
  • Growing scope and billsScope is locked at four decisions you approve.
  • Starting from zero162 ready-made blocks and industry blueprints.
  • Hiring a whole teamA crew of 8 or 9 roles does the work for you.
  • Lock-inStandard Python, Django and PostgreSQL code that is yours and runs anywhere.

ENTERPRISE SOFTWARE ARCHITECTURE · 7 PROVEN TOOLS

What your software is built on

Industry-standard tools, so any developer can read, run and extend what Luff builds for you.

  • Python

    The main programming language

  • Django

    The application backbone

  • PostgreSQL

    Your database

  • Next.js

    The web screens people use

  • TypeScript

    Safer, checked web code

  • Docker

    Packaged to run anywhere

  • Caddy

    Secure web address (HTTPS)

How each job flows

Every piece of work goes through the Brain first. It hands each job to the Luff Engine, which gives it to the cheapest worker that can do it well: most of it to the Local Intelligence System as solid, ordinary code, and AI only where it matters. The 80 : 15 : 5 split is the design target, not a measurement of your project.

You

Your request

In plain words

Luff Human Intelligence Brain

Decides if a job needs AI, and who does it

LUFF ENGINERuns the work

  • 80%Luff Local Intelligence SystemOrdinary code on your machines
  • 15%Jev, the judgeOptional, your OpenRouter account
  • 5%ClaudeYour Claude subscription

You get

Your final product

Built, tested, live

Inside the Luff Engine, about 80% of the work goes to the Luff Local Intelligence System, about 15% to Jev and about 5% to Claude.
  1. 80% · Luff Local Intelligence System

    Ordinary code, no AI needed

    Inside the Luff Engine, Luff's own Local Intelligence System does everything repeatable as ordinary code on your machines. It gives the same result every time, and none of it is billed as AI usage.

    • Screens and features from 162 ready-made blocks
    • Setting up and updating your database
    • Quality and security checks
    • Building and packaging your application
    • Testing, going live and secure connections

    $0.00 AI cost

  2. 15% · Jev, the judge

    A small, fast AI decides first

    Before any AI work starts, Jev decides whether it needs Claude at all, and which crew role should take it. It runs on your own OpenRouter account, sees only the first 300 characters of a message, and is off without a key. If it is unsure, the work simply goes to Claude.

    • Decides whether a task needs Claude
    • Sends work to the right crew role
    • Briefs each role with only the rules it needs

    Optional · your OpenRouter account

  3. 5% · Claude

    Deep reasoning, kept for what needs it

    The hardest thinking goes to Claude, through Claude Code on your Mac, under your own subscription. You pay Anthropic directly, and Luff adds nothing on top.

    • The overall design of your application
    • Complex custom logic
    • Problems no template covers

    Your Claude subscription

Ready-made building blocks
162
Automated build steps
13
Decisions you approve
4
Markup on your AI usage
$0.00

YOUR JOURNEY · 4 MILESTONES

You make four decisions. Everything between them is done for you.

Each milestone hands you something you can see, and nothing moves on until you approve. No standups, no tickets, no technical vocabulary.

  1. 01BlueprintSee your application before it is built
  2. 02DesignChoose the look, decide who sees what
  3. 03BuildYour crew builds it
  4. 04LaunchTest it, then go live

01 · Blueprint

See your application before it is built

Luff draws the screens of your application before any work starts. You correct them, and the plan is locked to what you approved, so the agreement is a picture, not a paragraph.

  • Screens you can see and correct
  • Your records named in your own words
  • The plan locked when you approve

Gate 01You get: Approved screens and a locked plan

Front desk

Patient record

Day sheet

Scope frozen against 3 approved screensApproved

Illustration

02 · Design

Choose the look, decide who sees what

Pick one of the ready-made themes and every screen changes to match it. Then decide who can see and do what, so access is settled before anything is built.

  • Ready-made visual themes
  • Pre-built screen elements
  • Who-sees-what access rules

Gate 02You get: A locked look and access plan

Owner · all recordsFront desk · bookingsClinician · own patients

Illustration

03 · Build

Your crew builds it

Your crew assembles the application from 162 ready-made building blocks. Every change is checked in a safe copy before it goes in, and your database is set up and kept up to date for you.

  • 162 ready-made building blocks
  • Every change checked before it goes in
  • Database set up and updated for you

Gate 03You get: A working application on your own servers

Ready-made building blocks162
  • Databaseset up and updated
  • Patient recordschecked, no issues
  • Booking screenchecked, no issues
  • Access ruleschecks passed

Illustration

04 · Launch

Test it, then go live

Your people try everything on a private test copy first. When you approve, the new version goes live with no downtime, and the previous version is kept ready in case you want to switch back.

  • Tested on a private copy first
  • Goes live with no downtime
  • One step to switch back

Gate 04You get: Live, with the previous version kept ready

Version

Current

Live now

Version

New

Tested, ready to go

  1. 01You approve the tested version
  2. 02Visitors move to the new version
  3. 03The secure connection moves with it
  4. 04The previous version is kept ready

Illustration

YOUR AUTONOMOUS CREW · TYPICAL DELIVERY 24 TO 72 HOURS

A core team of real roles, and a crew to speed it up.

Every project has a core team of 8 roles, or 9 when it includes a native phone app, and each piece of work goes to the role whose job it is. On top of that team, your crew size decides how many builders work at the same time, which decides how soon you get your application.

Showing all 8 roles for this scope

  • CS

    Chief of Staff

    Executive strategy

    Turns your requirements into a plan and keeps all the work pointed at them.

  • DM

    Delivery Manager

    Orchestration

    Plans the order of work and hands each piece to the role whose job it is.

  • PD

    Product Designer

    Experience

    Draws the screens and applies the theme you chose.

  • DA

    Database Architect

    Data

    Designs how your records are stored and keeps the database up to date.

  • WD

    Web App Developer

    Engineering

    Builds the dashboards, forms and features of the web application.

  • MD

    Mobile App Developer

    Engineering

    Unstaffed. Added when the project includes a native phone app.

  • AE

    AI Engineer

    Intelligence

    Adds search, summaries and any AI features the project needs.

  • DE

    DevOps Engineer

    Operations

    Runs the test copy, the switch to live and database backups on your own servers.

  • QA

    QA Analyst

    Assurance

    Runs the quality and security checks before anything goes live.

CREW SIZE · 3 OPTIONS

More builders, sooner delivery

Typical times. The 14-day trial can use every crew size.

  1. 01

    Split

    Your approved requirements are split into separate parts of the application.

  2. 02

    Build together

    Builders work on those parts at the same time: extra hands for the busiest roles, and separate build tracks for separate parts.

  3. 03

    Combine

    The master brings every part together into one application, checked as a whole before you see it.

  • Core Squad6 builders

    about 48 to 72 hours

    Standard web applications and first products.

    Every plan

  • Accelerated12 builders

    about 24 to 36 hours

    Business tools, patient portals and marketplaces.

    Pro and Enterprise

  • Swarm20 builders

    about 12 to 18 hours

    Hospital systems, finance platforms and large multi-role systems.

    Enterprise

INDUSTRY BLUEPRINTS · 3 READY TODAY

Start from your industry, not a blank page.

Pick a blueprint and your project starts with the ready-made blocks your industry needs, already checked and connected.

  • Healthcare and clinics

    Patient records, clinical charts and bed rosters, with separate access for doctors, nurses and admin staff, and patient details kept out of the browser.

    • Patient records
    • Bed and ward rosters
    • Doctor, nurse and admin access

    48 ready-made blocks

  • Finance and ledgers

    Double-entry accounts, tax and VAT in several currencies, invoices that cannot be changed once issued, and payment notifications handled safely.

    • Double-entry ledger
    • Multi-currency VAT
    • Locked invoices

    54 ready-made blocks

  • Software for many customers

    A separate, private space for each customer organisation, member invitations, a full history of every change, and billing per seat.

    • One space per customer
    • Member invites
    • Per-seat billing

    60 ready-made blocks

YOUR SOFTWARE, YOUR RULES

Own it. Run it anywhere.

Luff builds your software. It does not rent it back to you.

100% yours
Every line of code Luff writes belongs to you, from the first day.
No lock-in
Your software keeps running without the studio or its licence. Nothing ties it to Luff.
Runs anywhere
On a standard server for about $5 to $15 a month, on a server you already have, or on your own hardware.

PRIVATE BY DESIGN

Your records never leave the machines you choose.

No cloud account with us, nothing uploaded to us, no licence server to reach. The app never contacts Luff's servers on its own.

  • Nothing reported back

    The app never contacts withluff.com or any Luff server on its own. No tracking, no usage reports, no background syncing. Your files and records stay on the machines you choose.

    calls to Luff servers · 0

  • Your Claude, your subscription

    The work runs through Claude Code on your Mac, under your own Claude subscription. Luff adds no markup and never sees your passwords or keys.

    Your Claude account

  • A licence that works offline

    Your licence key is checked on your Mac itself. There is no licence server to contact, and nothing to confirm online to keep it working.

    Checked on your Mac

  • Jev is optional, and plainly disclosed

    Add your own OpenRouter key and Jev, the judge, decides whether a message needs Claude. It sees up to the first 300 characters of each chat message, under your key. Without a key, Jev is off and every message goes to Claude.

    LUFF_JEV_SEND_TEXT=0

124 LANGUAGES · 10 RIGHT TO LEFT

Software your people can actually read.

An operation in Bahrain runs its records in Arabic, right to left. A team in Kerala works in Malayalam. The app speaks 124 languages, and for right-to-left languages the whole layout flips automatically.

Showing 24 of 124 languages

Record screen · Arabicdir="rtl"

سجل المريض

الاسم
إميلي كارتر
الزيارة القادمة
الخميس، 10:30
الحالة
مؤكد
إرسال تذكير

WHO IT'S FOR

Built for the people who need software, not the ones who write it.

  • 01

    Clinics, schools and factories

    Get the systems your organisation runs on, without building an IT department to make them.

  • 02

    Marketing and digital agencies

    Deliver complete software projects to the clients who already trust you, without outsourcing the build.

  • 03

    Software houses

    Take on more projects with the team you already have, and hand your engineers the hard problems.

WHAT'S NEXT · 5 ON THE ROADMAP

Where Luff is going.

Everything above is in the app today. These are on the roadmap and not yet available.

  • Coming

    Native iPhone and Android apps

    Your applications as native phone apps, ready for the App Store and Google Play.

  • Coming

    Business email and domains

    Company email and web addresses for your applications, set up for you.

  • Coming

    Payments for your applications

    Take payments in the software Luff builds for you, including GCC payment methods.

  • Coming

    Round-the-clock monitoring

    Your live software watched day and night, with common problems fixed automatically.

  • Coming

    Jev as quality judge and safety check

    Jev reviewing test results before launch, and checking risky steps before they run.

PRICING · USD

Predictable pricing. No surprise AI bills.

One licence per Mac, paid monthly or yearly. You bring your own Claude subscription, and Luff adds no markup to it. Every Mac starts with a 14-day trial in the app.

  • Starter

    Solo founders and first products.

    $49/ month

    Billed monthly

    Crew size

    Core Squad · 6 builders

  • Pro

    Agencies and growing companies.

    $149/ month

    Billed monthly

    Crew size, up to

    Accelerated · 12 builders

  • Enterprise

    Software firms and institutions.

    $399/ month

    Billed monthly

    Crew size, up to

    Swarm · 20 builders

Every plan includes

  • The full studio: all four milestone gates
  • The core team of 8 roles, or 9 with a native phone app
  • Licence tied to your Mac, checked offline
  • Move to a new Mac up to twice a year
  • Fresh licence key in your portal on every renewal
  • No markup on AI: you use your own Claude subscription

Plans differ only in crew size: a bigger crew builds more of your application at the same time, so it finishes sooner. The 14-day trial can use every crew size. Your licence is tied to your Mac and valid through your paid period; renewals deliver a fresh licence key to your portal. Prices in US dollars; Paddle adds sales tax or VAT where your country requires it.

TECHNICAL AND LICENSING FAQ

Questions the answer has to be plain about.

What is the Luff Human Intelligence Brain?

It is the centre of Luff, and it decides the way an experienced person would: does this job need AI at all? Every piece of work in your project goes through it, and it holds together two architectures: an AI Architecture that solves the AI problem, and a Software Architecture that lets non-technical people build complex enterprise software. For each job it picks who does it: the Luff Local Intelligence System inside the Luff Engine for the routine 80%, Jev for the quick 15% of decisions, and Claude for the 5% that needs deep reasoning. That is how Luff keeps AI costs down while keeping your software well built.

How fast is delivery?

Typically 24 to 72 hours for a project, depending on its size and your crew size: about 48 to 72 hours with Core Squad (6), 24 to 36 with Accelerated (12), and 12 to 18 with Swarm (20). Time you take to review at the four milestones comes on top.

Where does my software run?

Wherever you choose: a standard cloud server for about $5 to $15 a month, a server you already have, or your own hardware. The code is yours, and it does not depend on Luff to keep running.

What do I need to bring?

A Mac with Apple silicon on macOS 13.0 or later, and your own Claude subscription with Claude Code installed and signed in. Luff does its work through Claude Code, under your account. Everything else comes with the app.

Does Luff send my code or data anywhere?

Not to Luff's servers. The app makes no hidden connections, sends no usage data and has no cloud syncing or backup. Work you ask Claude to do goes to Anthropic through your own Claude Code account, exactly as if you used Claude Code yourself.

What is Jev, and what does it see?

Jev is the judge in the 80:15:5 split: a small AI model that decides whether a message needs Claude before Claude is started. It is optional and runs on your own OpenRouter account: you add its key to the file ~/.luff/.env. It sees up to the first 300 characters of each chat message you write, sent to OpenRouter under your key. Set LUFF_JEV_SEND_TEXT=0 to stop the text being sent. With no key, Jev is off and every message goes to Claude as before. Nothing is sent to Luff's servers.

Can I try it before paying?

Yes. The app includes a 14-day trial with no sign-up. The trial can use every crew size, from Core Squad (6) to Swarm (20).

What is the difference between the plans?

Only the crew size. Starter builds with Core Squad (6 builders), Pro with up to Accelerated (12) and Enterprise with up to Swarm (20). A bigger crew builds more parts of your application at the same time, so it finishes sooner. Everything else, including all four milestones and the core team of 8 or 9 roles, is the same on every plan.

How does licensing work?

Your licence is tied to your Mac and valid through your paid period; renewals deliver a fresh licence key to your portal. After you pay, give us your Mac's ID, which the app shows when you choose Show this computer's ID. A key for that Mac is created automatically and sent to your email and portal; paste it into the app. It is checked on your Mac, with no licence server involved.

What if I replace my Mac?

Move your licence from the customer portal by entering the new Mac's ID. Each plan can move to a new Mac up to twice a calendar year. A fresh key for the new Mac is sent to your email and portal.

Is the 80:15:5 split a measurement?

No. It is the design target. About 80% of the work, such as building screens, setting up the database, quality checks and going live, is done by the Luff Local Intelligence System, inside the Luff Engine, as ordinary code on your own machines, with no AI involved. About 15% is decided by Jev, the small judge model. About 5% is deep reasoning by Claude, such as the overall design and problems no template covers. How the split falls depends on your project, and without an OpenRouter key Jev is off, so its share goes to Claude.

Why does macOS ask before opening the app?

If a version has not yet been through Apple's notarization check, macOS asks for confirmation the first time you open it. Right-click the app in Applications, choose Open, then confirm. You only need to do this once.

How do I get updates?

New versions are published on the Releases page, each with a SHA-256 fingerprint you can use to confirm the download is genuine. A Check for Updates button is coming in a later version of the app. It will only check when you click it, never on its own.

Who handles billing, tax and invoices?

Paddle is our merchant of record. It takes cards, Apple Pay and Google Pay in US dollars, calculates and remits sales tax or VAT for your country, and issues your invoices. Update your card, download invoices or cancel from the customer portal.

What happens to what I built if I stop paying?

The applications Luff built for you are yours, with all their code, on your own servers. They do not depend on the studio or its licence to keep running.

All 15 questions

Own your software instead of renting it.

Download the studio, describe what your organisation needs, and approve the first blueprint. The software is yours from day one.

Apple silicon · macOS 13.0 or later · 14-day trial, no sign-up