methmine

A closed room for operators. Entry by invitation.

The methmine window: the profile table at full width, with tags, egress and the state of every profile

The network layer is inherited, not imitated.

JA4 and HTTP/2 match, byte for byte, the Chrome build the browser claims to be. Not a promise: a check that runs in CI on every build.

Who is in the room matters more than what is in it.

Three rules by which people get in.

invitation

A member invites you under their own name and answers for you with their standing. Invites are few and earned, and members give them only to people they are prepared to answer for.

application

Without an inviter, applications are read when a window opens. Current members may be consulted before acceptance. Every application gets an answer after the window closes, either way.

terms

Price and terms are given at acceptance, not here. Leaving means leaving: the way back is a new invite.

Every screen.

The six screens an operator opens every day.

The whole fleet on one screen.

Folders, tags, egress and state in every row. A folder launches at once with one button, and a profile with no egress is visible before launch, not after.

The Profiles screen: profiles grouped in folders with tags, egress address and state

Endpoints kept once.

An address is stored once and assigned to profiles, so the fan-out on one exit is stated before the assignment, not discovered after it. If the supplier never said whether it rotates, the screen says so.

The Proxies screen: endpoints with credentials, rotation and the number of profiles on each

The decisions you would make again.

A template fixes what should repeat and never the machine itself. Every profile still draws its own seed, and the screen shows how many variants it has left.

The Templates screen: four templates with fixed facets and the number of variants left

Extensions, and what they cost.

The packages you brought, and what each costs the profiles carrying it. An extension signed by you exists nowhere else, and the screen is the first to say so.

The Extensions screen: packages with version, origin, probeable files and profile count

What is on the disk, and when it expires.

Login state lives thirty days, history twenty-six weeks. An expired key makes what it sealed unreadable, for us as much as for anyone.

The Storage screen: profiles by size, snapshots and name with totals for the installation

A journal of what touched your profiles.

What you did and what asked for access: the signed program got it, the unsigned one did not. Your disk, nobody else’s.

The Activity log screen: entries by day with refusals, launches and edits

Screens from the design build. The browser is in development.

What exists today.

Voice
Closed voice for members is live. It is what the room uses every day.
Browser
Being built for the members. Profiles stay on your disk and open with your passphrase; there is no copy in a cloud.
Entry
By invitation, or by an application read in the next window.

Application

Three fields. This is vetting, not a lead form.

Between windows an application waits for the next one. No payment details are asked for.

Telegram or email, where the answer goes.

The handle of a member.

In your own words: what you run, at what scale, for how long. If you are here to offer a partnership or sell something, proxies included, say so.