The company · how you work with us
You keep your store.
We return the intelligence.
Bunsar is an API company. You keep your storefront, your layout, your placement — we return JSON, and your own front-end decides where it goes. In production since 2019, built at İTÜ ARI.
What it removes
Bunsar deletes the data and consent work you are paying for today.
The engine works from what the shopper is doing right now — this session, not a profile built up about them over time. So there is no stored shopper profile to warehouse, no consent path to maintain for it, and no script of ours watching every page. It deletes work you are paying for elsewhere.
A CDP dependency
No stored profile to warehouse, join, or keep in sync for this to work.
A consent path
This feature adds no cookie banner and no consent path to maintain.
A tracking script
Nothing of ours has to sit on every page watching the shopper.
The cold-start dead zone
A first-time visitor has a session too — so there is no blank period before they ‘have a profile’.
Removing a legal and data workstream doesn’t just save engineering time — it takes a review off the critical path. That is what moves the date you go live.
The honest ceiling, said plainly: there is no shopper profile in our data model. That is not the same as ‘never touches disk’ — the session context is passed on the request and can land in ordinary edge logs. We claim there is no profile in our data model. We do not claim the data never touches disk.
bunsar session context, per callno shopper profile in the data model measured on Curated Products — see the capability page
What you send
One feed in. JSON back. Your front-end places it.
There is exactly one thing to hand us: an image-bearing product feed — the same catalogue you already publish. We read it, and we answer over the API in JSON. Where that JSON lands on the page is your call, in your own template. We touch nothing else.
- What you integrate is the feed — not your CMS, not your checkout, not your theme
- Your storefront stays yours: your layout, your placement, your brand
- We return data; your front-end renders it, exactly where you decide
- No rebuild, no re-platform, no tag on every page of your site
- What it needs: product images and basic attributes — and within the first two weeks we tell you whether your feed is clean enough
You send
Your product feed
An image-bearing catalogue feed — the one you already have.
We return
JSON, over the API
The engine reads your catalogue and answers in structured JSON — no markup, no widget.
You place
Your own front-end
Your template renders it where it belongs — the storefront stays yours.
estimated, to first integration · a bit longer if you have no front-end resource to place the results
Two weeks is what you put in, not what you get back — we are not quoting you a return. It is roughly what a first integration costs your team: small, bounded, and reversible.
What it costs to start
A first integration a GM can approve on their own.
Because the only thing you hand us is the feed, and because your storefront stays yours, there is very little to expose. A first integration is about two weeks of your team’s time, and we change nothing you depend on. A GM can greenlight this on their own, to see the engine on their own catalogue. The annual licence is the team decision that follows, once it has proven out.
- Bounded: the work is the feed and the placement, and it ends
- Reversible: nothing in your stack is rebuilt, so nothing has to be un-rebuilt
- Small enough that you can start on one module, on one surface — not a platform migration
- A decision a GM can make without opening a CFO business case
How you buy
An annual enterprise licence. You start with one module.
- It is an annual enterprise licence. Scoped to your catalogue and to the modules you turn on — not a seat count, not a metered bill.
- You start with one module on one surface. The narrowest thing that proves out on your own products — not the whole engine on day one.
- The rest turn on when you want them, on your own timetable. More modules, more surfaces: they switch on against the same integration. That is the architecture, not an upsell — you expand when it earns it.
The honesty contract
Every claim we make about the engine is backed by a real artifact.
This is the differentiator, and it is a promise you can check. Every capability claim on this site is backed by something real — a measurement, a measured result, or a named population. We publish the gaps, not just the wins: in our own demo catalogue, 1,664 pieces come back with no complete look around them — each one named, with what stopped it: a class this setup doesn’t dress, a piece it never reached for, a photo it couldn’t read, or no photo at all. Which one it is tells you whose job it is — a setting, a buy, or a shot. And we don’t show you a conversion chart we can’t reproduce. The proof is the capability pages themselves — read them and check the receipts.
Let’s put it on your catalogue.
Send us your feed and we’ll stand up a first integration on your own products — one module, one surface, about two weeks. You keep your store; we’ll show you the intelligence it returns.
Book a demo