Introducing InsForge Email

07 Mar 2026 • 3 minute
Tony Chang

Tony Chang

CTO & Co-Founder

InsForge Email

InsForge now supports sending transactional emails directly from your application. The email service is built on AWS SES, runs as a managed multi-tenant layer inside the InsForge cloud, and is accessible through the SDK with a single method call.

This feature is currently experimental and available exclusively on the Pro plan.

How It Works

The flow is straightforward:

  1. Your application calls emails.send() with recipients, subject, and HTML content.
  2. The SDK validates and authenticates the request against your project.
  3. InsForge Cloud queues the message and routes it through AWS SES.
  4. The email lands in the recipient's inbox.

You do not configure SES credentials, manage sending domains, or handle bounce processing. InsForge manages the infrastructure and sending reputation across tenants.

What You Can Do

  • Send transactional emails to up to 50 recipients per request
  • Include CC and BCC recipients
  • Use full HTML formatting for email content
  • Set custom sender display names for branding

This is designed for transactional use cases: order confirmations, password resets, onboarding sequences, notifications, and similar communications your users expect to receive.

Rate Limits

The Pro plan supports up to 50 emails per hour. Authentication emails (signup verification, password reset) are included on all plans. Custom transactional emails through the SDK require the Pro plan.

Sending an Email

typescript
const { data, error } = await client.emails.send({
  to: ['user@example.com'],
  subject: 'Your order has shipped',
  html: '<h1>Order #1234</h1><p>Your package is on the way.</p>',
});

That is the entire integration. No SMTP configuration, no third-party email provider setup.

Current Limitations

  • Email is an experimental feature. APIs and behavior may change.
  • The TypeScript SDK is the only client available today. Mobile SDK support is coming.
  • The service is scoped to transactional emails. Bulk marketing sends are not supported.
  • Recipient addresses should be validated before sending to maintain deliverability.

What's Next

We are monitoring usage patterns and feedback during the experimental phase. Rate limits, API surface, and plan availability may evolve as the feature stabilizes.

If you are on the Pro plan, you can start using it today. Read the full documentation at docs.insforge.dev/core-concepts/email/architecture.