Connect each client's PrestaShop, WooCommerce or Shopify store once, then hand that client a login that reaches their store and nothing else. Client logins don't use up your team seats.
Not the monthly price — the price per client store, because that is the line you either absorb or pass on.
€14,90
per client store, per month — with all 10 connected
€13,96
per client store, per month — with all 25 connected
Row allowances are per account, not per store, so a single very large client can eat into the room the others need. Worth a look at your biggest store's order table before you pick a tier.
You do this once, with credentials the client never has to hand around. Read-only, isolated, and it never touches their production database.
One email field on the database page. They get a login of their own — no shared password, nothing for you to keep in a spreadsheet.
Enforced in PostgreSQL, not just in the interface: even a request that skips our app entirely is refused a store the client wasn't granted.
It isn't white-label. Your client signs in at bequery.pro and sees BeQuery branding, not yours. There is no custom domain and no way to hide that we exist. If reselling under your own name is the requirement, this package doesn't meet it today.
It isn't per-client billing. One subscription, one invoice, one card. You bill your clients the way you already do — there's no revenue share and no reseller portal.
Limits are per account, not per client. Stores, rows and reports all come out of one shared allowance, so one heavy client affects what's left for the rest.
We would rather you find this out on this page than three clients in.
No. The member limit prices people working inside your account — your staff. A client login is how you deliver a database you already pay for, so it doesn't consume a seat. You are never choosing between hiring someone and onboarding a client.
No. Each store lives in its own isolated PostgreSQL schema, and a client's access is a grant on specific stores. The check runs inside the database itself, so it holds even for a caller that bypasses the BeQuery interface and talks to the data API directly. A store they weren't granted comes back as not found — they cannot even learn it exists.
Not yet. Your client signs in to BeQuery and sees BeQuery branding, at bequery.pro. If you need the product to carry your own name and domain, that isn't available today — we'd rather tell you now than after you've onboarded five clients.
No. You hold one subscription and one invoice for the whole account, and you bill your clients however you already bill them. There is no per-client billing, no revenue share and no reseller portal.
Revoke their access from the database page and it takes effect immediately. If that was the only store shared with them, they're removed from your account entirely — their login survives but reaches nothing of yours.
Yes, and it's worth checking before you commit. Plan limits apply to the whole account: Business covers 50 million rows across every store you connect, Scale covers 250 million. One very large store can therefore take up room the others need.
Connect a single store, invite the client, and see what they see before you move the rest of your book across.