Private preview · Capture mode live

Transactional email.
On your domain.

Your customers see your brand, your From address and your reply path. TEJL handles the verified sending subdomain, aligned authentication, typed message contract, recipient controls and day-two operations behind one stable API.

Become a design partner See the integration

Honest status: the gateway and hosted capture environment work today. Client-domain onboarding, production delivery, templates, recipient preferences, customer accounts and billing remain admission-gated roadmap capabilities—not live features.

POST /v1/messages

const message = await tejl.send({
  from: "appointments@notify.client.com",
  to: "customer@example.com",
  template: "welcome-v3",
  data: { firstName: "Mia" }
});

Acceptedidempotency checked

Policy passedsender + quota

Capturedproduction delivery gated

Client-owned domain

DKIM · SPF · DMARC

Typed messages

Recipient control

Managed operation

01 / The platform

Enterprise discipline,
without an internal email team.

Direct email APIs are inexpensive. Reliable, properly branded transactional email is an operating system of identity, policy, recipient state and evidence. TEJL Send builds and runs that layer for each client.

Stable application API

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

Safe message acceptance

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

Client-owned identity

Mail uses the client's verified sending subdomain, aligned Return-Path and approved reply mailbox—not a TEJL sender domain.

Managed operations

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

Recipient agency

Every managed template exposes a preference path. Optional mail can be stopped without requiring an account in the client application.

Evidence before promises

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

02 / Client identity

Your name in the inbox.
Your reputation protected.

We onboard a stable transactional subdomain under the client's DNS. TEJL infrastructure stays behind the contract—never in the visible From address or a hidden reply route.

Visible Fromappointments@notify.client.comClient-owned and DKIM authenticated

Return-Pathbounce.notify.client.comSeparate custom MAIL FROM with aligned SPF

Preference hostlinks.notify.client.comBranded HTTPS magic-link destination

Reply pathsupport@client.comRoutable client mailbox—or Reply-To is omitted

The admission contract

01
Prove ownership
The client or authorized DNS owner approves each hostname, sender and reply behavior.
02
Align authentication
2048-bit DKIM, custom MAIL FROM/SPF and monitored DMARC must pass before production.
03
Isolate operation
Each client receives an SES tenant, identity, configuration set, suppression scope and quotas.
04
Fail closed
If required DNS drifts, sending pauses. We do not silently fall back to a provider-branded Return-Path.

No hollow guarantees: aligned authentication and transactional subdomains reduce provider branding and help segment reputation; no responsible operator can promise inbox placement, a specific mail-client rendering or absolute isolation from parent-domain/provider reputation.

03 / Integration

Send a typed event.
Not arbitrary email.

1
Define
Approve message classes, form-event schemas, templates, locales and essential/optional policy.
2
Capture
Run your real application flow without sending externally or risking customer inboxes.
3
Admit
Verify the client domain, DNS, templates, events, complaint handling and production-provider access.
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 '{
    "messageClass": "purchase.receipt",
    "template": "receipt@4",
    "to": ["customer@example.com"],
    "locale": "hr-HR",
    "data": { "orderId": "1842" }
  }'

202 Accepted{ "status": "captured", "replayed": false }

Current API: raw HTML/text submission, status lookup, usage and suppressions are implemented in capture mode. The typed event shown above, template service, SDKs and customer-managed configuration are the production contract being built—not available endpoints today.

04 / Message and recipient control

Structured by design.
Controlled by the recipient.

Schema

Approved form events

Bookings, receipts, contact acknowledgements and security flows use provisioned schemas. Public form input can never choose arbitrary recipients, headers or HTML.

Template

Immutable, tested versions

Every template has typed variables, HTML and plain text, locale rules, managed footer controls, review history and rollback.

Markup

Truthful structured data

Supported orders, invoices or reservations may carry validated JSON-LD or Microdata after mailbox-provider registration. We do not inject fake schema into every message.

Magic link

Preferences without an account

An explicit client-branded link opens a narrow recipient session—no Marija Fitness or TEJL login. Ordinary opens and clicks never change preferences.

Unsubscribe

Correct for the message class

Optional and subscription mail gets one-click unsubscribe. Password resets, OTPs and essential receipts remain available only when genuinely triggered.

Evidence

Auditable recipient state

Preference changes, suppression reasons and provider events are separate, timestamped facts. Link-scanner noise is not treated as human intent.

Roadmap boundary: templates, structured-email markup, the magic-link preference center and one-click unsubscribe endpoint are specified production work. They are not implemented in the current capture preview.

05 / 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

06 / 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 client-owned sending identity
Capture-to-production DNS admission
Suppressions, monitoring and evidence
Business-hours support

Discuss Managed Core

Reliability Design-partner focus

€349/month

Onboarding from €1,500

Up to 100,000 accepted recipients
Multiple domains and environments
Delivery monitoring and reviews
Priority incident handling
Monthly reliability evidence

Discuss Reliability

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.

07 / Admission roadmap

Private preview now.
Production by evidence.

Now

Hosted capture gateway

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

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.

08 / 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.

Will email come from a TEJL domain or show a different reply address?

No. The production contract uses a verified client-owned From subdomain, a separate aligned client-owned MAIL FROM host and a routable client reply mailbox—or no Reply-To. Authentication reduces provider branding, but we cannot guarantee how every inbox renders a sender.

Does every recipient need a Marija Fitness or TEJL account?

No. The planned preference center uses a short-lived magic link scoped to one client and recipient. An explicit preference action changes state; an email open or ordinary click does not.

Can recipients unsubscribe from password resets and receipts?

Optional and subscription categories will support one-click unsubscribe. Security and essential transaction messages are classified separately and sent only when the underlying action requires them; every template still provides a clear preference or help path.

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

Transactional email.On your domain.

Enterprise discipline,without an internal email team.