Run your own
commerce platform.
Your brand, your domain, your plans, your prices, your clients. Galactic Core runs the commerce, Anvil generates the storefronts, and TLDP carries the deliveries — all three invisible underneath. You keep the relationship, set the pricing, and bill your clients directly. We bill you wholesale, and never touch your customers or their money.
Agencies sell projects. Platforms earn subscriptions.
Every client build ends. The retainer is renegotiated, the scope resets, and revenue starts from zero again next quarter. A platform is different: you onboard a merchant once and they pay every month for as long as they trade. The problem has always been that building a commerce platform is a multi-year engineering programme, and operating one is a permanent team. This is that platform, already built and already operated, with your name on it.
Same agency, same client, two business models.
What an agency charges for a storefront today, against what the same delivery costs on your own platform. The saving is real, but it is the side effect — what changes is what you are selling.
The build stops being the business.
Commerce, storefronts and logistics. Your brand on all three.
Most white-label commerce offers a storefront builder or a backend. You get the operation, the storefronts and the deliveries — already integrated, and all of it under your name.
Galactic CoreThe commerce your clients run on.
The full engine behind every merchant you onboard: catalog, checkout, payments, customers, inventory, accounting, analytics. Your clients get a complete commerce back office under your brand.
AnvilHow their storefronts get built.
Describe a store in plain language and get a production storefront wired to the engine. What used to be a six-week build becomes an afternoon, so your delivery cost per client collapses.
How their orders get delivered.
One integration over many couriers — rates, fulfilment, tracking, proof of delivery and returns. Your merchants ship through your logistics layer, and each courier invoice for their deliveries carries your brand rather than ours.
Because they are integrated, the back office acts and the storefront follows — so merchandising across a client portfolio stops being a ticket queue. Anything touching money is still a draft the merchant approves.
Sell them separately or as one offering. Commerce and logistics each stand alone, so you can take one now and the next when you are ready — and the integration between them is our problem, not yours.
Everything a software business needs, except the software.
You are not buying an app to rebrand. Six things arrive together as one kit — the product, the packaging, the pricing, the billing, the storefront and the upkeep. That is the whole apparatus of a software business, already built and already running.
The product
A commerce engine and a storefront generator, both under your brand.
The packaging
Your own tiers: how many, what each is called, what each includes.
The pricing
Flat monthly, a share of what the client sells, or both, at rates you set.
The billing
Your own payment account, your own invoices, your clients paying you.
The storefront
A shop for every client, in minutes rather than weeks.
The upkeep
Updates and repairs handled by the platform, not by your team.
What you supply: the clients, the brand, and the price.
What you actually control.
Your brand
Logo, favicon, colours, product naming, sign-in copy, support address. No Tybrite branding in any client-facing surface.
Your domain
Your own subdomain immediately; your own custom domain with automatic TLS.
Your plans
How many tiers, what each is called, what each costs, and what each one actually includes. Not a re-skin of our pricing: your own tiers, composed by you.
Your billing account
Your clients subscribe on your payment account. Their money never passes through us.
Your clients
Onboarding, accounts, and the relationship are yours. We have no channel to them.
Your team
Staff accounts with roles, so a delivery lead and an account manager see what they should.
Your look
Describe the interface you want and the platform generates it: palette, spacing, shape, navigation. Every generated palette is contrast-checked before you can ship it.
Your commerce plans are composed inside a limit set by your wholesale agreement — you can build any tier up to what you’ve bought, and never beyond it. That is the guarantee that a plan you sell always works: you choose what to include and what to charge; we make sure the capability is really there.
Logistics works slightly differently, and it is worth knowing before you price it: on TLDP you set your own prices and your own names on both payer sides, but the shipping tiers themselves are ours. You are re-pricing a plan that exists rather than composing a new one — which is what keeps a delivery limit you sold from being one the platform cannot honour.
Every client you add makes the others more useful.
Selling wholesale is a capability of a store here, not a separate product. So a retailer on your platform can order stock from a wholesaler on that same platform — quote, purchase order, invoice on terms — without either of them leaving their own admin. A business is a seller to the tier below it and a buyer to the tier above, using the account it already has.
The trading is live today — the ordering, the terms, the invoice, between any two businesses on your platform. Browsing for a supplier you don't already know is the part that arrives with volume: it stays switched off until there is enough supply behind it to be worth opening, because an empty directory is worse than none.
Your clients’ developers integrate with you.
Most white-label offers stop at the interface. Every agency here gets a branded API host, provisioned the day it is approved. Publish the API specification as your own, ship your own client library from it, and document it under your name. Your clients’ developers read your hostname, install your package, and never learn ours.
Wired the day you are approved. The URLs your clients hand to a payment provider or a shopping channel carry your name — and those outlive any interface, because they get pasted into somebody else’s system.
Turn it on and your own API specification is served live at your host: your server URL, your title, your key prefix, your name throughout. It regenerates as the platform gains capability, so it is never the stale copy.
A ready-made pipeline generates a typed client from your specification and publishes it under your own package name, on your own infrastructure. Your developers never write a client; we never hold a key that could publish to your customers.
Your pipeline pulls from a URL that is always correct, so a scheduled run does nothing until something actually changed. Nothing to wire up, nothing to keep in step by hand.
Request signatures and key formats stay ours — they are protocol rather than branding. A developer reading a header name is already inside the integration, and renaming it would describe an API nobody serves.
You set the price. We bill you wholesale.
There are two prices in this model and you control one of them. You decide what your clients pay you — per plan, per client, however you package it. We invoice you a wholesale rate for the merchants you have live. The spread is your margin, and it compounds with every client you keep.
Every merchant you onboard is revenue that recurs for as long as they trade.
Wholesale rate — confirm before launch. We publish no required retail price, so what you charge on top is yours to decide.
A merchant on a free trial costs you nothing.
You can offer a real trial exactly as we do, and only start paying when they convert to a paying store.
You can see the margin.
The portal shows what your clients pay you against what you owe us, per client, so you know which ones are actually profitable. It is a view, not a settlement — we never net the two or take a cut of the difference.
An agency that wants this under its own brand.
Development agencies
Stop rebuilding commerce for every client. Ship on an engine you didn’t write and don’t maintain.
Marketing and growth agencies
You already run the storefront, the campaigns and the funnel. Now own the platform underneath instead of renting someone else’s.
Design studios
Anvil turns the design you already sell into a working store, so the build stops being the bottleneck.
Consultancies and systems integrators
A platform to implement, extend and support, with the engine’s API and SDK behind it.
They never see us.
Your client signs in at your domain, to your brand, and runs their commerce from a back office with your name on it. Storefronts are generated under your brand. Support routes to your address. As far as they are concerned, you built the platform.
The commerce itself — orders, money, stock — is signed and settled by the engine. That trust layer stays ours, because it is what makes the whole thing safe to resell.
Multi-tenant, isolated, and the same engine everyone else runs.
Your platform is not a fork. It is the same commerce engine, with your tenancy isolated at the data layer and your brand resolved per hostname. That means you inherit every improvement we ship without a migration, and you never wait on us to port a feature to your copy. For agencies and clients that need it, dedicated isolated infrastructure is available rather than the shared platform.
Three steps to your own platform.
Apply
Tell us about your agency and the merchants you serve. The form is below.
Set it up
Brand, domain, plans, prices and your payment account — a working session with our engineers, not a support ticket.
Onboard your first client
Generate their storefront with Anvil, connect it to the engine, and start billing.
Technology partnership is a different conversation — see the partner tracks→
Your platform. Our engine.
Launch partners shape the programme and get the categories and territories that won’t be open twice.