services
Every part of the system

your register • keep it or own one

Keep your register, or own one outright.

Most places should keep the register their staff already knows and have online orders land in it. Square and Clover are open to build against. Or move to a register in the browser that you own, with loyalty and inventory in one place.

this part today

built

Working in our own kitchens: madebutter and the two at order.neonburro.com.

who does it

what it does

POS, part by part.

4 things it does for a restaurant, and the state each one is in today.

built

Working in our own kitchens: madebutter and the two at order.neonburro.com.

next

On the build list now.

for you

Made when a restaurant like yours asks for it.

Keep the one you have

Square and Clover are open to build against, so online orders land in them. Toast takes outside orders only through its partner program, which we are not in, and we say so before you sign.

for you

A register in the browser

Ring up the counter on any tablet, options and add ons priced right, the same menu as online. Running at madebutter.

built

A card reader wired in

Tap and chip on a reader tied to your own processor account. Today the register records the card payment by hand.

next

Watched for safety

cypher checks every connection that touches your payments.

built

yours forever

Built once. Owned forever. Nobody rents it back to you.

A custom app and web app made for your restaurant and handed over. No platform subscription, no cut of your orders and no lock in. The crew stays: the system grows with the business a part at a time, for as long as the business runs. If you ever leave, everything leaves with you.

what you own

The code

Every line, in a repository in your name.

The app

Your app in the stores under your own developer account.

The web app

Ordering, the menu and checkout on your own domain.

The guests

Every name, number and order, yours to export any day.

what still costs money, plainly

Card processing

What your processor charges, on your own account. We add nothing on top.

Hosting

Run it yourself for little or nothing, or have us run it. Your choice, and you can switch.

The app stores

Their own developer fee, paid in your name, only if you want a store app.

Changes later

Ask us or any developer. The code is yours, so nobody is locked in.

what changes

Rented today, yours tomorrow.

What most restaurants rent for this, and what they get instead.

rented today

yours

Switch everything to switch ordering

→ Keep the register your staff knows

A register leased with a contract

→ Or a register you own outright

Loyalty and inventory in other apps

→ All of it in one place

questions

Asked first.

Do I have to switch registers?

No. Keep yours and we route orders into it where it allows, or move to one you own. Your call.

Does owning the register remove card fees?

No. Card networks charge every register. Owning it removes the software rent and the lock in, not the processing fee.

Is it built?

The browser register runs at madebutter. Wiring a card reader into it is next.

kinds that lean on it most

are you a restaurant

Lower bills and orders in your own name.

Your own site, your own ordering and your name on every screen, built around how your kitchen already runs. Tell us what you use now and roughly what it costs, fees and cuts included, and we will show you the difference.

01

You tell us what you run on

The platform, the delivery apps, the register and the phone. Whatever it really is.

02

We order from you

Your site, your menu and your phone, the way a hungry guest meets them tonight.

03

You get a side by side

What you pay now, fees and cuts included, against what your own system would cost to run, line by line, before you decide anything.

What kind of place

What you pay a monthplatform, apps and fees, roughly

We read it. No sequence of emails after.