Teams & plans

Members and shared mailboxes

Every Fluxmail instance has at least one member. A personal instance uses one member to identify its owner. Team and Enterprise instances can add more people and decide which mailboxes each person can reach.

# A fresh instance starts with one logged-in administrator
fluxmail setup --name "Ada Lovelace" --email ada@example.com

# Administrators invite more people
fluxmail members add --name "Grace Hopper" --email grace@example.com
fluxmail members list

# Members connect mailboxes they own
fluxmail accounts add gmail

# Reassign an existing mailbox
fluxmail accounts assign <account-id> --owner grace@example.com

# Choose who else can reach it
fluxmail accounts access <account-id> --owner-only
fluxmail accounts access <account-id> --shared
fluxmail accounts access <account-id> --share-with ada@example.com

fluxmail members add prints an enrollment code once. Send it to the new member through a private channel. They add the instance and set their password with fluxmail login --instance <name> --server <url> --enroll.

--owner-only makes a mailbox private to its owner. --shared makes it available to every active member, including members added later. Repeat --share-with to give selected members access. The administrator role permits member, license, key, and mailbox metadata management. It does not grant access to another member's private mail.

Stdio uses the member logged in to the selected local instance. You can limit a connection to selected mailboxes that member can already reach:

# Local connection for the logged-in member, limited to one mailbox
fluxmail stdio --account <account-id>

# HTTP connection for the logged-in member, limited to one mailbox and read-only actions
fluxmail apikey create \
  --name "ada laptop" \
  --account <account-id> \
  --profile read-only

Update an HTTP key's mailbox allowlist without replacing the key:

fluxmail apikey accounts <key-id> --account <account-id>
fluxmail apikey accounts <key-id> --all-accounts

Member and mailbox scope control which mailboxes a connection can reach. Its permission profile separately controls which email actions the client can take. Use one key per client so you can change its scope, change its permissions, or revoke it without interrupting other connections.

Plans and licensing

Self-hosting is free on the Personal plan: 3 connected mailboxes and 1 member. Pro raises the mailbox limit for one person. Team and Enterprise add members and more mailboxes. On Team and Enterprise, each person connects their own mailboxes, and a mailbox can also be shared. See pricing for current limits.

You can buy Pro or Team from the pricing page. Stripe returns you to Fluxmail after payment and shows your license key. Copy it then, and keep it private.

Use Manage subscription on the pricing page or license screen to update your card, view invoices, change plans, or cancel. Stripe asks for the email used at checkout and sends a one-time passcode before opening billing details. Stripe billing emails also include the same portal link.

Unlock a paid plan with your license key:

fluxmail license activate
fluxmail license status

Fluxmail prompts for the key without displaying it. For automation, use fluxmail license activate --key-file /absolute/path/to/license, or pass - to read from stdin.

An administrative REST client can read the same status from GET /api/v1/admin/license, activate a key with POST /api/v1/admin/license/activate, and deactivate it with DELETE /api/v1/admin/license. An API key needs admin.license; an administrator's member session can call the routes directly. The status response never includes the configured license key. REST cannot replace or remove a key supplied through FLUXMAIL_LICENSE_KEY.

One license activates one instance, and enforcement keeps working offline. If you schedule a cancellation, the paid plan works until the end of the billing period. After the subscription ends or a payment fails, the instance drops back to Personal limits. Deactivating, downgrading, or lapsing never deletes mailboxes or data.

Software license

Fluxmail is source available under the Elastic License 2.0. You may use, modify, create derivative works, and redistribute it subject to that license. A fork does not need a paid Fluxmail subscription merely because it is a fork. Without a valid paid key, Fluxmail uses the Personal plan with 3 mailboxes and 1 member.

Official Pro and Team entitlements require a valid Fluxmail license key. ELv2 does not allow you to change or circumvent license key functionality or remove functionality protected by a key. It also does not allow you to provide Fluxmail to third parties as a hosted or managed service that exposes a substantial set of its features.

The software license does not grant rights to Fluxmail names or logos beyond applicable law. Their use is subject to the Fluxmail Terms of Service.