PROTON ACCOUNT CREATOR

Proton account creation with the cost, progress, and result in view.

Use a focused Proton workflow for individual requests or repeatable tasks without losing the provider-specific price and operational context.

Create Proton →See how it works

✓ Failed items use zero credits · No subscription

CREATE TASK

ProviderProton

Quantity100 accounts

Estimated total200 credits

Failed? Credits returned.

THE SHORT VERSION

Choose Proton, set the quantity, review the 2-credit-per-account estimate, and follow one task from submission to reconciled output.

Provider rate2 credits

Per successful Proton account

Access methods2

Dashboard and REST API

Task lifecycleVisible

Progress, partial results, and completion

100%credit-back guarantee

Successful accounts consume credits. Failed accounts do not. Any credits reserved for a failed item return to your MailMaker balance automatically.

Read the guarantee →

Proton batches are best treated as purpose-specific work rather than generic volume. Teams should document why privacy-oriented mailbox coverage is required and how completed credentials will be protected.

Restrict access to Proton result exports and define a removal policy before a high-volume task begins.

MailMaker keeps the Proton rate visible at 2 credits per successful account. The estimate is calculated before the request starts, so provider selection and cost remain one decision rather than two disconnected steps.

Privacy-product QA
Provider-diversity test environments
Controlled API tasks with explicit ownership

Selecting a privacy-oriented mailbox provider does not protect credentials after they leave the creation workflow. The value of a Proton batch depends on who can access the export, where it is stored, and when it is removed—not only on the provider name.

Use Proton when the product or test plan genuinely needs Proton Mail coverage. Assign the receiving owner and restricted destination before creating the task so the result is never parked in a broad support channel or general analytics log.

Privacy-product email testing
Restricted credential handoff
Provider-diversity coverage
Two-credit cost model

MailMaker charges 2 credits only for each successfully completed Proton account. Any item the task reports as failed uses zero credits; if credits were reserved while it processed, they return to the workspace balance automatically.

This guarantee protects the account-creation charge. It does not claim that a third-party provider will keep an account active forever or exempt the customer from the provider's rules. The task result and credit ledger remain the source of truth for what completed and what was returned.

Successful item: provider rate is charged
Failed item: zero credits used
Reserved credit: returned automatically
Partial task: pay only for successful results

A request creates a stable task ID with its provider, quantity, estimated credits, and status. Operators can see whether the work is queued, processing, completed, partial, or failed instead of inferring progress from elapsed time.

For Proton, the pilot should test access-controlled storage and deletion as carefully as task completion because privacy-oriented coverage loses value when credentials are handled broadly.

Review quantity and cost before submission
Keep the task ID with the internal request
Compare requested, successful, and failed totals
Export only after reconciliation

The dashboard is useful for direct operations and review. The API exposes the same provider, quantity, task states, result retrieval, and credit model to an internal system.

A Proton bot should write result data only to the designated secure destination and keep raw credentials out of polling logs and general observability systems.

Starting with the visible dashboard workflow helps a team understand the task lifecycle before moving the same decisions into unattended automation.

At the current rate, 10 successful Proton accounts use 20 credits, 50 use 100, and 100 use 200. These examples are estimates for completed output, not a promise that every submitted item will finish successfully.

Compare the estimate with the available balance and leave room for a controlled replacement task when a batch finishes partially. For recurring work, attach the credit estimate to the internal request so the requesting team understands the cost before an operator or integration approves execution.

10-account validation estimate
50-account operational estimate
100-account scale estimate
Remaining balance after approval

Queued means the task has been accepted but work has not finished. Processing means the task is active. Completed means the final result is ready for reconciliation, while partial means some output exists but failures still require review. Failed means the task did not produce a usable completed result.

Do not release credentials based only on elapsed time. Retrieve the authoritative task, compare the counters, and preserve the task ID with the exported result. This makes support, cost review, and later cleanup possible without reconstructing state from memory.

Queued: retain the task ID and wait
Processing: monitor without duplicate submission
Partial: separate usable output and failures
Completed: reconcile before handoff
Failed: inspect cause before retrying

Confirm that the provider matches the actual requirement, that the requester is authorized, and that a named owner will receive the result. Review quantity, credit estimate, environment, export format, retention period, and the secure destination before pressing create.

For Proton, the pilot should test access-controlled storage and deletion as carefully as task completion because privacy-oriented coverage loses value when credentials are handled broadly.

Provider and purpose confirmed
Quantity and credit budget approved
Task owner recorded
Secure result destination prepared
Retention or deletion date documented

The final record should answer five questions: what was requested, what completed, what failed, how many credits were used, and who received the output. A file without that context is difficult to audit and easy to misuse.

Keep raw credentials separate from normal analytics and support logs. Share only through the approved destination, restrict access to the smallest practical group, and remove exports when the documented workflow no longer needs them.

QUESTIONS

What teams ask before they start.

Does choosing Proton automatically secure the exported credentials?−

No. The customer must still use an approved access-controlled destination, restrict recipients, and remove the export when it is no longer required.

What should be logged for a Proton task?+

Keep task metadata such as state, counts, duration, and credit usage. Do not place passwords or recovery data in normal logs.

What is a Proton account creator?+

It is a task-based workflow for requesting Proton accounts, reviewing the expected credit cost, monitoring progress, and retrieving reconciled results.

How many credits does one Proton account use?+

Proton currently uses 2 MailMaker credits per successfully completed account.

Can Proton account tasks use the API?+

Yes. The MailMaker API supports the same provider selection, quantity, task-state, status retrieval, and result workflow available through the dashboard.

What happens if an account fails?+

Failed items do not consume credits. If credits were reserved while the task processed, they are returned to the workspace balance automatically; a partial task is charged only for its successful results.

READY WHEN YOU ARE

Credits in. Accounts out.

Start with the provider already selected. If an item fails, its credits return automatically.

Create Proton →

Proton account creation with the cost, progress, and result in view.

Choose a Proton account creator for a Proton requirement.

Proton coverage is most useful when privacy expectations extend to result handling.

A failed account never becomes a paid result.

One task carries the complete operating record.

Use Proton manually today and automate it when the workflow is ready.

Translate Proton quantity into a credit budget before submitting.

Each task state should trigger a different operational response.

A practical checklist before the first Proton task.

A result is useful only when it can be explained and owned.

What teams ask before they start.

Credits in. Accounts out.

Proton account creation with the cost, progress, and result in view.

Choose a Proton account creator for a Proton requirement.

Proton coverage is most useful when privacy expectations extend to result handling.

A failed account never becomes a paid result.

One task carries the complete operating record.

Use Proton manually today and automate it when the workflow is ready.

Translate Proton quantity into a credit budget before submitting.

Each task state should trigger a different operational response.

A practical checklist before the first Proton task.

A result is useful only when it can be explained and owned.

What teams ask before they start.

Build the complete workflow.

Credits in. Accounts out.