BulkForge is a bulk email orchestration service for teams that run on Azure. You compose and send from a hosted dashboard, but the sending itself is done by an agent that you deploy into your own Azure subscription. The agent reads your Postmark token, Azure Communication Services (ACS) connection string, or SendGrid API key from your own Key Vault, so those credentials are never given to BulkForge. BulkForge is not an email provider: messages are delivered through your own Postmark, ACS, or SendGrid account.
THE PROBLEM Most bulk email tools ask you to paste a provider API key into the vendor's dashboard, which puts a sending credential on infrastructure you do not control. BulkForge keeps the credential in your tenant and adds a job queue, routing between providers, and a per-recipient send record on top of the accounts you already have.
WHO IT IS FOR Azure-based teams that send appointment reminders, alerts, and operational notices to a list of recipients, and want the provider credential to stay under their own governance. Typical users are IT, operations, and application teams in healthcare, financial services, and enterprise IT.
HOW IT WORKS
Subscribe on the Azure Marketplace and sign in to the dashboard with a Microsoft work or school (Entra ID) account.
Deploy the Customer Agent into your own resource group from the Marketplace. The template provisions a Function App, a Key Vault, and a storage account. Enter your provider credentials during deployment or later; they go into your Key Vault.
In the dashboard, load an audience (CSV, pasted JSON, or a list of addresses), choose message content (an HTML file, a synced Postmark template, or the built-in editor with a live preview), pick the sender and the agent, and send.
The agent polls the hosted service for jobs, sends through your provider, and reports each recipient's result back. The agent starts every connection itself.
WHAT YOU GET
One compose screen: audience, content, sender, and target agent
Three delivery providers: Postmark, Azure Communication Services Email, and SendGrid, with configurable channel priority and a fallback channel
Dry run: pushes a job through validation and routing without sending anything; it does not count against your monthly sends
Per-recipient audit trail: accepted or failed with the provider's reason, the channel used, the provider message ID, and a timestamp, exportable as JSON or CSV
A job summary with failures grouped by reason
Optional completion webhook: BulkForge posts a JSON summary to an HTTPS URL you provide when a job finishes
Workflow Trigger API: start a send from Power Automate, Logic Apps, or your own code with a single REST call (details below)
Azure Communication Services send limits: set your own hourly and per-minute limits, and switch batch sending on or off, under Manage Agents
Agent status in the dashboard, with the agent's version and last heartbeat
WORKFLOW TRIGGER API POST /api/workflows/trigger, authenticated with a BulkForge API key (a bfk_ key you create in the dashboard) sent as a bearer token. The body names the agent and carries the recipients, with optional message content or a saved template ID, an idempotency key, a scheduled time, and a completion webhook URL. The same key can read a job's report and download its audit export. This is the only external API; BulkForge has no separate public API for contacts or campaigns. A ready-made OpenAPI file can be imported into Power Automate as a custom connector.
SECURITY MODEL Delivery credentials stay in your Key Vault and are read by the agent through managed identity. The hosted service does not store or receive them. It does store what it needs to hand a job to your agent: the recipient addresses, any per-recipient template data, the subject and message content, the per-recipient audit records, saved templates, and job counters. A daily sweep clears the stored content of finished jobs after a retention period and deletes audit records after a longer one; the periods are listed in the install guide. A job whose content has been cleared cannot be re-sent from the dashboard. The hosted service runs in Azure.
WHAT BULKFORGE DOES NOT DO
It is not an email provider and does not deliver mail itself.
It records whether the provider accepted or rejected each message at send time. It does not receive bounce, complaint, delivery, or open events, so "accepted" does not mean "delivered".
It has no unsubscribe handling, suppression-list management, open or click tracking, A/B testing, or drip sequences, and it does not keep a contact database; audiences are uploaded per send.
Scheduled sends are set through the API, not in the dashboard.
With Azure Communication Services batch sending on, an address on Azure's suppression list inside a batch can be dropped without a failure being recorded. Batch sending can be switched off, and each recipient is then sent separately.
It is not a compliance certification, and it does not make your messages compliant with email law.
PLANS Free, $0/month: 500 sends per month, 1 agent, no credit card. Starter, $49/month: 25,000 sends per month, 1 agent. Pro, $199/month: no BulkForge cap on sends, unlimited agents. Your email provider's own limits still apply. All plans include the dashboard, the three providers, routing and fallback, and the audit trail. Plans are flat-rate by monthly send volume and number of agents, not per seat. Sends are counted per recipient, per calendar month. Azure resource costs for the agent are billed separately by Azure.
COMMON QUESTIONS Does BulkForge see my provider credentials? No. They are stored in your Key Vault and read by the agent in your subscription. Does BulkForge store my recipient list and message text? Yes, for the retention period, so the agent can fetch the job. See the security model above. Is it an alternative to Postmark, ACS, or SendGrid? No. It sends through them, using your accounts. Can I try it first? Yes. The Free plan includes 500 sends per month with no credit card. Is there a direct integration with InsightForge? No. They are separate products with no direct integration.
Who Is the Company Behind Bulkforge?