Speckled mug
180 kr
SAASIE FOR A WEBSHOP
A shop
of your own.
Batteries
included.
Say what you sell and how you want it to feel. A code agent builds the shop, deploys it, and gives you the address it is running at. The database, the deploys, the numbers and the mail are already in the box.
hallgren ceramics
BASKET · 2
Deep bowl
340 kr
Checkout →
ORDER 0042 · PAID · 2 MIN AGO
Your storefront ✦ Your prices ✦ Your customers ✦ Your address
IN THE BOX
Four things you
never have to find.
A shop is not one thing. It is a storefront, somewhere to keep the orders, an address people can reach, and a way of knowing what happened. Only the first of those is interesting, so the platform brings the other three.
Somewhere to keep the orders
Products, baskets, orders, and the customer asking where theirs has got to. A Postgres database is created, connected and kept running before your shop serves its first request. You never see a connection string, and there is nothing to set up on the day you get busy.
An address people can reach
The shop answers at yourshop.saasie.app over HTTPS from the moment the name is claimed. No host to choose, no certificate to renew, and no preview build to graduate from — what your agent deployed is the shop that is open.
Numbers you can ask about
The analytics battery counts the things a shop cares about — baskets started, checkouts finished, which item keeps getting looked at and not bought. Your shop records them as they happen, and you can ask it how the last month went whenever you want to know.
Mail that leaves the building
The mail battery gives the shop its own sending address, so it can tell you an order came in without you standing up a mail provider. It is a handful of messages a day, not a newsletter — which is the honest shape of it, and why customer receipts belong with whoever takes the payment.
Words you did not have to write
The AI battery writes the product descriptions you have been putting off, turns a week of customer messages into the three things people actually keep asking, and lets a shopper search for “something warm for a winter wedding” and be shown the right shelf. No AI subscription, and no key to paste anywhere.
SHOPS WORTH OPENING
Small catalogue.
Real customers.
The shops that suit this are the ones no platform was ever built for: forty products, one person packing them, and a way of selling that is specific to what you make.
Kiln fired
on Sunday.
One-off pieces, sold once. When it is gone the page says so.
↗Order by
Thursday.
Pre-orders for a weekend bake, closing when the dough is mixed.
↗Merch for
the tour.
Shirts and records, up the week the dates are announced.
↗HOW IT WORKS
From “I should sell
these” to open.
- 01
Describe the shop
What you sell, roughly how many of them, and how you want people to pay. Say it the way you would say it to a friend — the agent makes the product and technical decisions from there.
- 02
The agent builds and deploys it
Storefront, basket, checkout, an order list only you can see. It is real code in a real repository, built and rolled out on every push, and you are never the one holding it.
- 03
Put your things in it
Photos, prices, the words that make somebody want one. This is the part nobody can do for you, and it is the only part that is left.
- 04
Change it by asking
A discount code before Christmas. Postage to Norway. A waiting list for the thing that sold out in an hour. Each one is a sentence to your agent and a deploy a few minutes later, not a plugin you hope still works next year.
NOT YOUR JOB
The shop platform,
skipped.
Everything a shop actually needs is here. What is missing is the apparatus that usually comes attached to it.
- ✕
A cut of every sale
What your customers pay goes to your own payment account. The platform runs the shop; it never sits between you and the money.
- ✕
A theme to fight
Nothing to bend into shape and no template to work around. The shop looks the way you asked for it to look, because that is what was built.
- ✕
An app store
No add-ons, no subscriptions stacked on the subscription, and no feature that arrives with someone else’s terms attached. What you need gets built into the shop.
- ✕
A server
No hosting to pick, no database to run, no deploy pipeline to wire up. It is all there, connected, from the first minute the shop is live.
What we ask of you is an email address, and a code from your inbox once. That is the entire list.
WORTH BEING PLAIN ABOUT
What this
is not.
- The money is not ours
- Payments run through your own account with whoever you already use. Payouts, refunds and the awkward conversation about a lost parcel stay between you, your customer and your provider. We are not in that loop and do not want to be.
- It is not a mailing list
- The mail battery is a small pipe — enough for the shop to tell you something happened. Receipts at volume, and anything you send on purpose to customers, belong with your payment provider or a sender you choose.
- It is not a catalogue importer
- There is no spreadsheet to map and no migration wizard. If you have a list of products already, hand it to your agent and it writes the import — once, for your shop, and then it is done.
- It is not built for a warehouse
- A Saasie is one container and one shared database, which is the right size for a studio, a bakery or a band. A shop that outgrows that asks for more and gets it — but it is worth knowing which end you are starting from.
YOUR SHOP, YOUR RULES