Your Mildport account

Everything you need to run Mildport lives in one place: your account. Sign up, create a key, and run a real import in the browser — the free plan is instant and needs no card.

The account is the front door for both paths. Whether you use our hosted engine or run your own, the same page issues the license and the same key works in both.

Sign up and create a key

1. Create your account, then your organization. One account can belong to several organizations — you pick which one you’re working in from the switcher.
2. Open Licenses → New tenant + license. Choose a plan. Free is instant; paid plans go through checkout unless your deployment is set up for direct self-serve.
3. Copy the key. It appears once, right after minting — it is never stored, not even by us. Lost it? Regenerate on the same page, then swap the key in your embed right away: on Mildport cloud the replaced key may stop being accepted at any time. (Self-hosted keys keep their full term.)

A tenant is one licensed context — one set of limits, one usage counter. Most products need one; agencies and platforms often create one per customer. With several tenants, the tenant switcher in the top bar picks which one the panel’s pages operate on.

No pasting inside your account

The pages that talk to the engine — Playground, Catalogs, AI settings, Learning & recipes, Deliveries, Changesets — don’t ask you to paste anything. Pick a tenant in the top bar and the panel fetches a short-lived key for it automatically: your signed-in account is the credential. These automatic keys live only in that browser tab, are pinned to the panel’s web origin, and expire on their own after a short while — your real license key stays where you put it. Pasting a key still works everywhere, and is the way in for operator-managed plans.

Try it in the playground

The Playground runs the real widget against the real engine, on your key. It is the fastest way to see what your users will see.

• No key to paste: the playground uses an automatic short-lived key for the tenant picked in the top bar (a just-minted key is picked up straight away, too).
• Download sample CSV gives you a file that pairs with the sample catalog — headers that need mapping, and a couple of untidy rows so the cleaning step has something to do.
• Launch the importer, drop the file in, map the columns, apply. Imports here are real: they run on the engine and count toward your plan.

That last point is deliberate. A sandbox that doesn’t count teaches you nothing about your limits; the playground shows you exactly what production will feel like.

Watch your usage

Usage shows the current month per tenant — imports, rows against your plan’s ceiling, and AI runs if you use them. Rows are counted as they are applied, so the number moves while you are in the playground.

Hitting a ceiling is not an outage: the limit applies per import, and the panel tells you which one you met. Change plans on the Licenses page and the new limits apply to the next key you issue.

Keep an eye on expiry

Keys are time-limited. Thirty days out, the account emails whoever created the key, and the license card starts showing a countdown. Renewing is the same regenerate button — the fresh key arrives immediately; make swapping the key in your embed part of the same sitting, since on Mildport cloud the replaced key may stop being accepted at any time. (Self-hosted keys keep their full term.)

Going self-hosted

The Self-hosting tab is where a paid account requests access to our container images and picks up the public key its engine will verify licenses against. Same license, your infrastructure — see Image access and the self-hosting overview.

Who can do what

• Organization owners create tenants, mint and regenerate keys, and request image access.
• Members see licenses, activity and usage, and can work the engine pages — playground, catalogs, AI settings, learning, deliveries, changesets — with automatic keys.

Invite teammates from the Members tab; they get an email and land in the same organization.

Next: Quickstart · Configure the widget