Private preview · Capture mode live

Transactional email.
Heavy lifting included.

Give your application one stable API. TEJL handles provider integration, sender onboarding, delivery policy, suppressions, event normalization and day-two operations.

Honest status: the gateway and hosted capture environment work today. Production delivery, customer accounts and billing remain admission-gated and are not represented as live.

POST /v1/messages
const message = await tejl.send({
  from: "welcome@yourdomain.com",
  to: "customer@example.com",
  template: "welcome-v3",
  data: { firstName: "Mia" }
});
Acceptedidempotency checked
Policy passedsender + quota
Capturedproduction delivery gated

One API

Provider-neutral

EU-first operation

Managed onboarding

Built for evidence

01 / The platform

A delivery control plane,
not another raw provider account.

Direct email APIs are inexpensive. Reliable transactional email is not. TEJL Send places policy, provider portability and operations between your application and the delivery network.

01

Stable application API

Integrate once. Provider credentials stay out of customer applications, and a provider change does not force a product rewrite.

02

Safe message acceptance

Required idempotency keys, tenant boundaries, quotas and sender policies stop common duplication and misuse paths.

03

Deliverability controls

Bounces, complaints and manual suppressions become normalized product state instead of scattered provider-specific logic.

04

Managed operations

TEJL owns onboarding runbooks, configuration review, monitoring, incident response and delivery-provider coordination.

05

Privacy-aware defaults

Current message bodies are neither persisted nor returned. Logs redact authorization, webhook secrets and request payloads.

06

Evidence before promises

Capture mode exercises the real acceptance path without external delivery. Production is enabled only after its gates pass.

02 / Integration

Plug in a message.
Get an operation.

  1. 1

    Connect

    Receive a tenant-scoped credential, SDK guidance and test sender policy.

  2. 2

    Capture

    Run your real application flow without sending externally or risking customer inboxes.

  3. 3

    Admit

    Verify domains, DNS, templates, events, complaint handling and production-provider access.

  4. 4

    Operate

    TEJL monitors the gateway and handles routine delivery infrastructure work under the selected service tier.

cURL
curl https://tejl-send.tejl.com/v1/messages \
  -H "Authorization: Bearer <tenant-key>" \
  -H "Idempotency-Key: order-1842-receipt" \
  -H "Content-Type: application/json" \
  --data '{
    "from": "receipts@yourdomain.com",
    "to": ["customer@example.com"],
    "subject": "Your receipt",
    "text": "Thank you for your order."
  }'
202 Accepted{ "status": "captured", "replayed": false }

Current API: raw HTML/text message submission, status lookup, usage and suppressions are implemented. Template APIs, SDKs and customer-managed configuration are roadmap items.

03 / Reliability model

Designed to fail safely,
then recover deliberately.

Your appone authenticated request
TEJL Sendpolicy · queue · state · events
Delivery networkprovider selected per policy
Implemented now
  • PostgreSQL persistence
  • Idempotent acceptance
  • Tenant-scoped authentication
  • Quota and sender enforcement
  • Suppressions and normalized events
  • Health/readiness probes
  • Capture and SES adapters
Required for production scale
  • Durable queue and retry scheduler
  • Outbox/worker separation
  • Signed customer webhooks
  • Metrics, tracing and SLO alerts
  • Multi-provider failover
  • Backups and restore drills
  • Regional continuity plan
Required for enterprise
  • SSO, RBAC and audit logs
  • Domain self-service and DKIM
  • Template/version management
  • Usage metering and billing
  • DPA, subprocessors and retention controls
  • Security assurance program
  • Support and incident commitments

04 / Commercial model

Pay for delivery infrastructure
you do not have to operate.

Private-preview pricing is a managed-service proposal, not a commodity email markup. Final limits and SLAs will be validated with design partners before public sale.

Managed Core

€149/month

Onboarding from €750

  • Up to 25,000 accepted recipients
  • One sending domain and environment
  • Capture-to-production onboarding
  • Suppressions, monitoring and evidence
  • Business-hours support
Discuss Managed Core

Enterprise

Custom

Scoped onboarding

  • Volume and retention design
  • Dedicated tenancy options
  • SSO, RBAC and audit requirements
  • Contracted support and SLOs
  • Security/compliance review
Plan an enterprise review

Preview assumptions exclude VAT and extraordinary provider, dedicated-IP or custom compliance costs. No card is collected on this site.

05 / Admission roadmap

Private preview now.
Production by evidence.

Now

Hosted capture gateway

Real authenticated acceptance, persistence, policy and event behavior without external email delivery.

Next

Design-partner pilot

Validate onboarding, templates, domain ownership, traffic shape, support expectations and willingness to pay.

Gate 3

Production delivery

Enable only after sender identities, DKIM, MAIL FROM, provider production access, events and runbooks pass.

Gate 4

Self-service application

Accounts, RBAC, domains, templates, API keys, logs, usage and billing become customer-operable.

Gate 5

Enterprise assurance

Contracted SLOs, audit evidence, disaster recovery, security controls and regional options.

06 / Questions

Before you plug in.

Is TEJL Send delivering production email today?

No. The hosted gateway is intentionally in capture mode. It accepts and records test traffic but sends no external email. Production admission is a separate verified step.

Why not integrate directly with an email provider?

You can. TEJL Send is for teams that value a stable application contract and want sender onboarding, policy, events, monitoring and provider operations handled as one managed layer.

Does the current version have a dashboard or login?

No. Login, dashboard, documentation portal and customer self-service controls on this page are non-functional pre-launch previews. They never ask for credentials.

Is TEJL Send enterprise ready now?

Not yet. The core gateway proves important boundaries, but enterprise readiness requires the queued delivery architecture, observability, customer administration, compliance evidence and operational gates listed above.

Design partner intake / 2026

Bring the app.
Leave the email operations.

Talk to TEJL