01
Manage
Everything about the subscription itself.
- Plans, billing cycles and seats
- Cost, estimated and actually billed
- Renewal dates and trial endings, on a calendar
- Payment methods, as type and last four digits
- Every plan change kept in history
Subscriptions and access
A secure workspace for managing subscriptions and everything that goes with them: logins, MFA codes, billing and who has access.
Free during early access. No card needed.
For individuals, teams, startups and businesses that manage more than a few subscriptions.

Why it's different
Subment manages everything around a subscription, from the plan to the audit trail, so access is granted, used and taken back in one place.
Subscription
Plan, billing and renewal
Credentials
Encrypted, masked until revealed
MFA
Codes generated on demand
Access
View, Use or Manage, per subscription
People
Workspace members and roles
Audit
Who opened what, and when
The problem
The plan is the easy part. Everything around it ends up in different places, and nobody can answer the questions that matter.
One subscription, five places
The subscription
Plan, seats, renewal date
In the vendor's own dashboard
The password
The login that unlocks it
Somewhere else entirely
The MFA code
The second factor
On one person's phone
The billing
What it costs, and when
In a spreadsheet
The access
Who can use it
In chats, and in memory
Subment gives the subscription a home.
The idea
Behind every subscription there's a plan and a price, but also a login, a second factor and the people who use it. Subment treats them as one connected thing, not five separate ones.
The centre of it all
Subscription
Credentials
The login that unlocks it
Authentication
The MFA and recovery codes
People
Who uses it, and in which role
Access
What each person may see or do
Billing
Price, cycle, seats and card
Subment keeps everything connected to the subscription in one secure place.
The Subment difference
Most teams hold their subscriptions together with tools that were never meant to talk to each other. Subment replaces the patchwork with one connected workspace.
The usual way7 tools
Nothing links them, so someone has to remember how.
With Subment1 workspace
One subscription workspace
One subscription, with everything that belongs to it attached.
Where logins live
The usual way: A spreadsheet, a chat thread, someone's memory
With Subment: On the subscription, encrypted and masked
Who can see a password
The usual way: Anyone who has the file
With Subment: Only people you choose. Others can use it without seeing it
Two-factor codes
The usual way: On one person's phone
With Subment: Generated on demand for people with access
Renewals
The usual way: A calendar entry, if someone made one
With Subment: Dashboard and calendar, before they bill
When someone leaves
The usual way: Change everything and hope
With Subment: Remove access, and see what they opened
The product
Everything Subment does is one of three jobs, and all three happen around the same subscription.
01
Everything about the subscription itself.
02
Everything that unlocks it.
03
Everything about the people who use it.
01 · Manage
Plans, billing cycles, renewal dates, seats and pricing in one list, with the rest of each subscription one click away.

02 · Secure
The saved login, its two-factor codes and the people who can use them are on the subscription they belong to. No hunting through other tools.

03 · Share
Subscriptions and people are organized by workspace, so each team sees its own. Decide who can open each subscription and what they see when they do.


Try it
Four small, working models of how Subment handles sensitive access. It's sample data only, and nothing you do here is sent anywhere.
01
A saved password stays hidden. Revealing or copying it is a deliberate act, and it leaves a line in the activity log.
Team admin login
•••••••••••
Masked until someone asks to see it.
Activity
02
Two-factor codes are generated when someone needs one, with the same countdown your phone shows.
Authenticator · Notion
--- ---
A live code from a demo secret. It's computed in your browser the same way an authenticator app does (RFC 6238), and it changes every 30 seconds.
03
Share a login with a contractor without pasting it into chat. Make a link, open it, then try to open it again.
What should the person see?
Link expires after
04
View, Use or Manage: pick one for each person and see exactly what changes for them.
Access to Slack
Who it's for
Keep your own subscriptions, logins and renewals in one place, and see what renews before it bills.
Share access without sharing passwords in chats. Everyone gets what they need, and it's recorded.
Centralize your SaaS stack and who owns each account as the team grows, and take access back the day someone leaves.
Manage the subscription lifecycle: billing, roles, per-subscription access and offboarding, with an activity log to show who opened what.
Security and trust
Subment holds the details that unlock your subscriptions, so this is what it stores, how it's protected, who can reach it, and what we don't claim yet. Every line describes what is built today.
Stored encrypted
Logins and API keys, TOTP secrets and recovery codes.
Stored, scoped to your workspace
Subscriptions, plans, costs and renewals, plus members, roles and activity.
Kept minimal
Payment methods are type, provider, last four digits and a nickname. There is no field for a full card number.
How is sensitive data protected?
At rest, each secret is encrypted individually with AES-256-GCM before it is stored, each workspace under its own key, which is itself protected by a key management service. In transit, traffic between your browser and Subment is sent over HTTPS.
How is my account protected?
Account passwords are hashed with Argon2id, and two-factor sign-in is available. Sign-in tokens live in httpOnly cookies that page scripts cannot read, and sign-in and sensitive actions are rate-limited.
Who can access it?
Only members of a workspace, by role, and per subscription at View, Use or Manage. Permissions are checked on the server every time, and access to one workspace never extends to another.
What happens to a credential?
Stored encrypted, listed masked, revealed only on request by someone permitted. Revealing or copying a login, or generating a 2FA code, asks for a recent sign-in confirmation. Exports never contain passwords, keys or 2FA codes.
How is access logged?
Revealing a password or generating a code is recorded with who and when, and never with the secret itself. When someone leaves, the log shows what they opened.

Early access
Subment is early, and it's open. You can create an account today. It's free while we shape it, and Early Access is temporary. That's also why this page has no customer logos, testimonials or numbers we can't stand behind.
Early product access
Use the working product now, free, with no card. Expect rough edges and change.
A say in what's built
Ask for features from inside the app, and tell us what you'd change.
No surprises
You'll get notice before paid plans start, and nothing you've stored is deleted or locked because of a plan.
Where the product is today. No dates, no promises.
Working today
In development
Coming later
Questions
Subment is a secure workspace for managing subscriptions and everything needed to access and run them: plans and billing, saved logins, 2FA codes, and the people who use each one. It's for individuals, teams, startups and businesses, and it's in early access.
A password manager stores logins. Subment is built around the subscription: its plan, cost and renewal, the credentials that unlock it, its 2FA codes, and who on your team can use it. It overlaps with a password manager where logins are concerned, so keep your personal passwords wherever you like.
Yes. Set each person's access to a subscription to View, Use or Manage. At Use, someone can copy a password or a 2FA code to sign in but can't see the password in plain text; that takes Manage. Copying still puts it on their clipboard, so this is controlled and recorded access, not a guarantee against a determined person. You can also send a one-time link that opens once, then stops working.
A subscription's TOTP secret is encrypted like any other secret. When someone with access asks for a code, Subment generates it, with the same countdown an authenticator app shows, and records that in the activity log. Recovery codes are kept with the subscription. Verification codes sent by email or SMS will come with the OTP inbox, which is still in development.
Yes. Create a team workspace, invite members and give each a role. Each workspace has its own subscriptions, people and encryption key, and agencies can keep each client in a workspace of their own.
Yes. Every account has a personal workspace for your own subscriptions, logins and renewals, separate from any team workspace. It's included on every plan and doesn't count toward your team workspace limit. Your plan's subscription limit is one total across all the workspaces you own, personal included.
Open their offboarding view to see everything they could reach, take that access back in one step, and get a checklist of the logins they knew. Subment can't change a password at the vendor for you, so the checklist ticks itself off as you change them. Removing someone ends their access on their next request, and the activity log shows what they opened.
Secrets are encrypted individually with AES-256-GCM before they're stored, each workspace under its own key. Account passwords are hashed with Argon2id, sessions use httpOnly cookies, and sign-in and sensitive actions are rate-limited. Two-factor sign-in is available, and revealing or copying a login asks for a recent sign-in confirmation, so a session left open on a laptop isn't enough on its own. The Security section has the full list.
Secrets are encrypted before they're stored, and the activity log never contains them. But the service holds what it needs to decrypt a secret when an authorized person asks to reveal it. That's what lets it generate 2FA codes and share a login with a teammate. We'd rather tell you that than imply otherwise.
No. A zero-knowledge design would mean the service can never decrypt your secrets, which would rule out generating 2FA codes and sharing a login on your behalf. We chose to make those work, and to say so plainly. If key management ever changes, this page will change with it.
None yet. Subment holds no security certifications, such as SOC 2 or ISO 27001, and has no independent audit report to share. If that changes, it will be listed here.
We'll publish hosting and data-location details on this page as soon as they're final. We'd rather wait than promise something we might have to take back. You can export your subscriptions as CSV or JSON, download everything held about you, and delete your account, all from Settings. Exports never contain passwords, keys or 2FA codes.
Nothing while Subment is in early access, which is temporary: everything is free and no card is needed. Paid plans are planned, and the planned prices are on the pricing page. Nothing you've stored is ever deleted or locked because of a plan, and you'll get notice before anything changes.
Free during early access. No card needed.
Not ready yet? Leave your email and we'll tell you when paid plans start. No spam.