This document tracks features, improvements, and ideas that are intentionally deferred from the initial MVP. These items are valuable but not essential for the first release.
Status: Queued for Phase 2 Description: Implement an AI-powered content policy checker that scans outgoing emails for:
- Spam patterns and suspicious content
- Phishing attempts or malicious URLs
- Content that violates platform terms of service
- Inappropriate or harmful material
Implementation Notes:
- Use Claude Haiku for fast, cost-effective content analysis
- Run asynchronously in the worker pipeline before SMTP send
- Configurable strictness levels (strict/moderate/permissive)
- Whitelist for trusted senders
- Appeal/review queue for false positives
- Log all blocked emails for audit purposes
API Design:
// Response when email blocked
{
"id": "msg_abc123",
"status": "blocked",
"reason": {
"code": "policy_violation",
"category": "spam",
"confidence": 0.94
}
}Status: Queued for Phase 2
Description: Add POST /v1/sms/send endpoint with Telnyx carrier integration
Scope:
- US and Canada phone numbers (E.164 format)
- Standard SMS (160 chars) and concatenated messages
- Delivery status webhooks
- MCP tool:
opensend_send_sms
Not in scope:
- International SMS (complex carrier agreements)
- WhatsApp or RCS
- Inbound SMS / 2-way conversations
Status: Queued for Phase 2 Description: Allow up to 100 emails per API request
API:
POST /v1/email/send/batch
{
"messages": [
{"to": "a@example.com", "subject": "Hi A", "body": "..."},
{"to": "b@example.com", "subject": "Hi B", "body": "..."}
]
}Description: Automated IP warmup scheduling for new dedicated IPs
- Gradual volume increase over 4-6 weeks
- Domain reputation monitoring
- Automatic throttling on reputation dips
Description: CLI-based dashboard for deliverability metrics
- Bounce rates by domain
- Spam complaint rates
- Inbox placement estimates
- Reputation scores from major providers
Description: Pre-configured deployment templates for hosted version
- Railway template with PostgreSQL addon
- Fly.io configuration with global edge
- Environment variable setup wizards
Languages to support:
- Python (
pip install opensend) - Node.js (
npm install @opensend/sdk) - Go (
go get github.com/opensend/sdk-go) - Ruby (
gem install opensend)
Description: Simple Handlebars/Mustache templating
{
"to": "{{email}}",
"subject": "Welcome, {{name}}!",
"template_id": "tmpl_welcome",
"variables": {"name": "Alice", "email": "alice@example.com"}
}Description: Receive emails at *.inbound.opensend.dev and forward to webhooks
- Parse attachments
- Extract plain text and HTML
- Spam filtering
- Custom routing rules
Description: SAML/OIDC integration for enterprise customers
Description: Complete audit trail of all API actions
- Who accessed what data
- Configuration changes
- Immutable log storage
- SIEM integration
Description: Organization-level management for agencies/resellers
- Sub-accounts with usage limits
- Billing aggregation
- Usage reporting
Description: Self-service dedicated IP provisioning
- IP allocation
- Reputation monitoring
- Automatic failover to shared pool
Regions to consider:
- UK (after US/Canada)
- EU (GDPR complexity)
- Australia/NZ
- India (complex regulations)
Description: API error messages and documentation in multiple languages
Description: Deploy in EU, APAC regions for data sovereignty requirements
These are ideas that need more research before committing:
- Email validation service - Check email deliverability before sending
- Sender reputation API - Let users check their domain reputation
- A/B subject line testing - Light analytics for testing subjects
- Calendar invite support - Native .ics attachment handling
- PGP encryption - End-to-end encrypted email option
- Scheduled sending - Send at a specific future time
- Email preview - Render email in major client simulators
- Unsubscribe link hosting - Managed unsubscribe pages
- BIMI support - Brand indicators for message identification
- ARC signing - Authenticated Received Chain for forwarding
- Add Redis caching layer when needed
- Implement connection pooling for high-volume scenarios
- Add horizontal worker scaling
- OpenTelemetry integration
- Structured logging with correlation IDs
- Metrics export (Prometheus format)
- Distributed tracing
- Rate limiting per endpoint (not just per key)
- IP allowlisting for API keys
- Webhook signature verification improvements
- Security audit by external firm
- Load testing suite
- Chaos engineering tests
- End-to-end test automation
Found something missing? Want to prioritize a feature?
- Open an issue with the
feature-requestlabel - Describe the use case and expected behavior
- Vote on existing issues to help prioritize
The community's input helps shape what gets built next.
Last updated: 2026-01-28