Your AWS SES. Your dedicated Mailat. See how it works
Documentation

Your first Mailat instance.

The path from choosing a plan to sending your first message.

Before you begin

You’ll need an email address you can access, an AWS account with SES enabled, and a domain you own with access to its DNS settings. AWS usage is charged to your AWS account separately from your hosting subscription.

Two places, two jobs.

Mailat.co is your hosting and subscription control panel. Your dedicated Mailat instance is your email application: inbox, sender identities, domains and email APIs.

1. Sign in with your email

Choose a plan on the pricing page, then enter your email on the sign-in screen. Open the magic link from your inbox. It expires after 15 minutes and can only be used once.

Use the same email for your Mailat account and your Gumroad purchase so your subscription can be matched to your account. If a link expires or has already been used, request a fresh one.

2. Choose your subscription

Basic is $15/month, Dedicated is $19/month and Enterprise is $50/month. Review the configured plan details and complete payment through Gumroad. Your selected plan is carried through sign-in to the billing page.

When you return, Mailat checks your subscription state. If payment confirmation is still pending, allow time for verification and refresh the billing status. Do not purchase again just because confirmation is delayed.

3. Connect AWS and deploy

  1. Open setup in your dashboard and choose an available instance name and domain option.
  2. Enter your AWS Access Key ID, Secret Access Key and SES region. Follow the AWS guide before sharing credentials.
  3. Validate the connection, review the configuration, then start deployment once.
  4. Follow the deployment stages in your dashboard. If you leave the page, return to the same instance to see its current state.
  5. Use Open Mailat when the instance is ready and complete any first-access instructions shown.
Readiness takes as long as the underlying steps need.

Provisioning, DNS and application checks can finish at different times. A pending or failed step is not a ready instance. Use the reported error or contact support before starting another deployment.

4. Connect your email domains

Inside your Mailat instance, open Domains, add a domain you own and follow its generated authentication records. Verify the DNS results before sending from that domain.

Start with sending only if you want to keep receiving mail in another service. Mailat receiving is an explicit additional setup. The domain guide explains which records do what.

5. Connect APIs and workflows

Open the API documentation in your Mailat instance and create an API key with the permissions your integration needs. Use that instance’s API base URL, not the Mailat.co hosting control panel.

HTTP-based workflow tools such as n8n can call the email APIs and receive webhook events. Verify webhook signatures, store secrets outside workflow source, and handle duplicate event IDs. The instance documentation contains the exact request formats and retry behavior.

Manage your account and billing

Your dashboard contains your instances, projects, billing, support and account settings. Open Billing to view your verified subscription state and manage the membership through Gumroad.

A cancelled renewal and an ended subscription are different states. Access through a verified paid-through date is shown in your dashboard. Review the subscription terms and contact support before changes that affect your data or hosting.

For email content and sender identities, open your Mailat instance. For a hosting problem, use Mailat.co support.

All guidesOpen your dashboard