# Email aliases for startups

> Organize startup email addresses for customers, security reports, hiring and press, with guidance on inbox ownership and when to use mailboxes.

Startup email addresses should make it easy for customers, candidates, and partners to reach the right team. A few well-named addresses on your company domain can clarify where messages go, but each one needs an owner and a reliable response process.

## Startup email address examples

| Address | Good for | Before publishing |
| --- | --- | --- |
| `hello@` | General questions and introductions | Decide who checks it and how often |
| `support@` | Customer product questions | Set a triage and response owner |
| `security@` | Responsible vulnerability reports | Limit access to the people who handle security |
| `press@` | Media and public relations | Assign someone to monitor requests |
| `careers@` | Job applications | Review access and retention for candidate messages |
| `billing@` | Invoices and payment questions | Route to an appropriate finance owner |

Use names that remain understandable as the company grows. Avoid creating several overlapping addresses such as `team@`, `contact@`, and `hello@` unless each has a clear role.

## Make ownership explicit

For every public address, record who monitors it, who can access its destination, and what should happen when that person is unavailable. A forwarded address may reach an existing inbox, but it does not provide team assignment, message tracking, or service-level guarantees by itself.

If a group needs shared history, separate user accounts, retention controls, or administrative access, compare hosted email or a shared inbox with basic forwarding. The [forwarding versus hosting guide](https://cyandb.com/email-forwarding-vs-hosting/) covers the tradeoffs.

## Add addresses without disrupting mail

Verify domain ownership, select and verify destinations, and review current DNS before changing mail routing. MX records affect incoming delivery, so follow the current instructions from your chosen provider and plan changes before relying on a new address. Read the [DNS setup guide](https://cyandb.com/dns-setup/) and [how domain forwarding works](https://cyandb.com/how-it-works/).

For general naming help, see [professional email alias ideas](https://cyandb.com/alias-ideas/) and the [small business forwarding guide](https://cyandb.com/small-business-email-forwarding/).

## Frequently asked questions

Which email addresses should a startup create first?

Start with addresses that match current responsibilities, such as `hello@`, `support@`, and `billing@`. Add security, press, or hiring addresses when someone is prepared to monitor them.

Should startup addresses forward to founders?

That can work for an early, simple setup, but define who is responsible and how access changes as the team grows. Sensitive topics may need a more restricted destination.

Is email forwarding enough for a startup team?

It depends on the team's needs. Forwarding can route incoming messages to existing inboxes, while hosted mail or a shared inbox may provide separate accounts, storage, sending, and collaboration features.

CyanDB’s current routing provider is a mock. It does not deliver or forward real email, and CyanDB does not change DNS records automatically.

## Bring your email setup into focus.

Create a workspace to organize domains, destinations, and aliases.

[Create your workspace](https://app.cyandb.com/signup)