Working on Linode (Akamai Cloud): Services, Account Security, Billing and Email Limits

Linode, now part of Akamai Cloud, has long been a favorite of individual developers and small teams because the interface is straightforward and the pricing is predictable. This guide covers the services on offer, the account security features built into Cloud Manager, how Linode’s post-paid billing works, and the SMTP port restriction that applies to some new accounts. For regions and first steps, see our Linode getting-started guide.

What you can build on Linode #

At the time of writing, Shared CPU plans start at a few dollars per month and Dedicated, High Memory and GPU plans scale up from there; the official pricing page has current numbers. Linode’s “developer friendly” reputation comes from letting people concentrate on application logic rather than infrastructure complexity, which suits web apps, API backends, development environments and data processing jobs.

Securing a Linode account #

1. Enable two-factor authentication. Linode’s own documentation calls 2FA essential because it acts as a second layer when a password may be compromised.
2. Configure security questions. Cloud Manager lets you set three security questions used to verify you as the account owner if you need to regain access.
3. Review Login History. Cloud Manager shows login attempts over the last 90 days, including date, source IP address and whether the attempt succeeded. Check it periodically.
4. Use SSH keys for Linode access and disable password authentication on the server.
5. Attach Cloud Firewalls to each Linode and allow only required inbound traffic.
6. Create user accounts with limited permissions for team members instead of sharing the primary login.

Management essentials #

• Tags: tag Linodes, volumes and NodeBalancers by project or environment for filtering and cost review.
• Backups: enable the Backup service for important Linodes and take manual snapshots before major changes.
• User permissions: grant each user only the resources and actions they need; Cloud Manager supports per-resource permissions.
• API and CLI: the Linode API and CLI cover all Cloud Manager functions for scripted management.
• Service transfers: Linode supports moving Linodes and DNS records between two Linode accounts you control through the Service Transfers section of Cloud Manager, with support tickets from both accounts. Block Storage volumes must be detached first, and transferring a Linode with the Backup service transfers its backup history. This is designed for reorganizing your own accounts or handing a client project to the client’s account, not for trading accounts.

How Linode billing works #

• Post-paid and pro-rated. Services accrue hourly charges through the month and are billed to your primary payment method at the end of the month, or sooner if accrued charges reach your billing limit.
• Hourly with monthly caps. Each plan has a monthly cap; once the cap is reached you pay the monthly rate.
• Active means billed. Charges accrue for any active service even if it is powered off. Delete services you no longer need.
• Promotional credit. New accounts may be offered a promotional credit for a limited period under Linode’s current terms.
• Payment methods. Credit and debit cards, PayPal, Google Pay and Alipay are accepted at the time of writing.
• Free control plane. LKE clusters are billed for worker nodes only.

Keep costs predictable by right-sizing plans, deleting idle Linodes, watching transfer usage and reviewing the billing page monthly.

Email from a Linode: the SMTP port policy #

To fight spam originating from its network, Akamai Cloud blocks outbound connections on ports 25, 465 and 587 by default on some new accounts. Self-hosted mail servers are difficult to secure and easily flagged as spam, so the restriction protects the reputation of the platform’s IP ranges. If you need to send email, open a support ticket explaining the use case to request an unblock, or use a transactional email service that works over an HTTPS API. Our guide to SMTP port 25 on cloud servers compares provider policies, and the SPF, DKIM and DMARC guide covers the records you will need in either case.

How teams use Linode #

Developers keep client and side projects apart with tags and separate user permissions, and use Shared CPU plans for environments that do not need consistent performance. Startups run production on Dedicated CPU Linodes with Managed Databases behind NodeBalancers, then move to LKE as service count grows. App teams combine LKE or plain Linodes with Object Storage for assets and Cloud Firewalls for the edge. Agencies ask each client to own their account and add the agency as a restricted user, which keeps billing and ownership with the client and makes hand-over a permission change.

A first-week checklist #

1. Enable 2FA, set security questions and check Login History.
2. Add SSH keys and create the first Linode with password login disabled.
3. Attach a Cloud Firewall allowing only the ports the application needs.
4. Enable the Backup service for anything stateful.
5. Tag everything and review the billing page at the end of the first month.
6. Choose an email path (authenticated relay or API provider) before the application needs to send.

Official references #

The Akamai Cloud (Linode) documentation covers products, billing and account security. Our Linode platform overview summarizes the platform and how to sign up officially.

Frequently asked questions #

Can I send email from my Linode?

On some new accounts, ports 25, 465 and 587 are blocked by default. Request an unblock through support with a description of your use case, or use an email API provider.

How do I manage my Linode account?

Through Cloud Manager in a browser, or the Linode API and CLI for automation.

Is a powered-off Linode free?

No. Charges accrue for any active service. Delete Linodes you are not using.