Fixed Addresses
Part of the MountDev Ops Workspace documentation. Updated November 15, 2026
MountDev Ops Workspace documentation | Updated November 15, 2026
Our Commitment MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
A fixed address is one address that never changes, just for your account. Use it for services that accept calls only from an address they know. It is in Settings, Connections, Fixed Addresses, for owners, admins, and anyone whose role allows managing connections. See Fixed Outbound Address for the shared address every connection can use for free. Anyone whose role allows it (owners and admins at first; the permission is called Manage fixed addresses in Settings, Permissions) can use this page. It shows only where a data region has a place to build in; a region with none says "Fixed addresses are not available for your data region yet."
Two Ways to Get One
- Use Your Own AWS (free from us). We build the same server in your Amazon Lightsail account. AWS bills you directly. This is built.
- Get a Fixed Address (paid) (Planned). We build and run a server just for you and bill the price shown when you buy. Billing starts when the address is ready.
Use Your Own AWS: Exactly What Happens
Before anything is built you see a review screen. Nothing is created until you select Build It in My AWS.
What is created in your AWS account. Each one is tagged mountdev-fixed-address with the server's random name, so you can find it in Lightsail:
| What | What it is for |
|---|---|
| One Lightsail server (the smallest Linux size, Ubuntu 24.04, in the region you pick) | Runs the small program that passes your calls along |
| One Static IP, attached to the server | The one address that never changes |
| Firewall rules: port 443 open, every other port closed | Lets only secure calls in |
What it costs. About $5 to $7 a month, billed by AWS to you. That is an estimate from AWS's public Lightsail pricing for the size and region, with the date it was checked. AWS can change its prices. See AWS's Lightsail pricing. A Static IP that is not attached to a server is charged by AWS, so we attach it right away and the removal steps delete it first.
The access we need. An AWS key that can only manage Lightsail and cannot delete anything. This is the whole policy:
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Action": [
"lightsail:CreateInstances", "lightsail:GetInstance", "lightsail:GetInstances", "lightsail:GetInstanceState",
"lightsail:AllocateStaticIp", "lightsail:AttachStaticIp", "lightsail:GetStaticIp",
"lightsail:PutInstancePublicPorts", "lightsail:GetInstancePortStates",
"lightsail:GetBundles", "lightsail:GetBlueprints", "lightsail:GetRegions", "lightsail:TagResource"
],
"Resource": "*"
}]
}We use the key only while setting up. When your address is ready, we erase our copy, and every check after that goes through the fixed address itself, not AWS. Delete the key in AWS too: IAM, Users, your user, Security credentials, the key, Actions, Delete.
Releasing an Address
- Your own AWS. Releasing stops MountDev Ops from using the address. It never deletes anything in your AWS account. Your server stays, and AWS keeps charging you, until you delete it yourself. Every service that allows the address, such as WP Cloud, will start refusing calls from it. Do these steps in this order:
- In MountDev Ops, move or turn off every connection that uses the address.
- Sign in to the AWS console and open Lightsail.
- Pick the region the server is in, then select Networking in the top menu, then the Static IPs tab.
- Find the Static IP named on the Release screen, select its three dots, then Delete, and confirm. Once deleted, that address is gone and cannot be brought back.
- Select Instances in the top menu, find the server named on the screen, select its three dots, then Delete, and confirm.
- The next day, open Billing and Cost Management and check that no Lightsail charge is left.
- If you still have the setup key, delete it as above.
- A paid address (Planned). We keep it for 14 days after you release it so you can get it back. It is never deleted because of an unpaid invoice alone; deleting it takes a confirmation. Billing ends at the end of the month you already paid.
What You See on the Page
Each address shows its name, whether it is managed or yours, its status (Working, Setting Up, Not Answering, Held), the address with a Copy button, its place, when it was last checked and how long it took to answer, its monthly cost, and every connection that uses it. Check Now checks it. Use for a Connection picks which connections send from it. A connection that uses your own address never sends from the shared address or directly: if the address is down, its calls wait and are tried again.
How It Is Built
Select Use Your Own AWS. Step 1 asks for a name, your Amazon Lightsail key (or picks the one you saved), and the place inside your data region. Step 2 is the review (action core.fixed_addresses.review): what will be created, the estimate, and the access it needs. Build It in My AWS (action core.fixed_addresses.create_own, owners and admins) starts it. Then the steps run on their own, and you can leave the page:
- Server created. One Lightsail server, tagged
mountdev-fixed-address, with a random name that holds nothing about you. - Address attached. One Static IP, attached and tagged, and every port but 443 closed.
- Installing. We wait for the server to say Running.
- Testing it. A signed check to the server. Only when it passes is the address shown, and the address is Ready.
A step that does not work is tried again after 1, 2, 5, and 15 minutes, then every hour, for up to 2 hours, and never makes a second server or a second address. After 2 hours it says which step did not work and why, keeps what it built, and waits for you: Try Again (action core.fixed_addresses.retry) starts the steps over, and needs the AWS key saved again once it was erased. You can have one setup running at a time and up to 3 fixed addresses.
Owners and admins get a notice when an address is ready, when it needs attention, when it stops answering (after two checks in a row fail), and when it answers again. Never one for every check.
The Page
Settings, Connections, Fixed Addresses (action core.fixed_addresses.list; one address is core.fixed_addresses.get):
- Check Now (action
core.fixed_addresses.check_now) checks it at once and says how long it took. The workspace also checks every address that is ready about every 30 minutes. - Use for a Connection (action
core.fixed_addresses.use) picks the address each connection sends from, the shared address or this one. Remove beside a connection (actioncore.fixed_addresses.remove_connection) sends only that connection from the shared address again. A connection on your own address never sends from the shared address or directly: with the address down, its calls wait and are tried again. - Release (action
core.fixed_addresses.release) asks what the connections that use the address should do (send from the shared address, or turn their fixed address off), then shows the steps above for deleting it in Lightsail. Nothing is deleted for you. - Each address says Working, Setting Up, Not Answering, Needs Attention, or Released, and shows its place, when it was last checked, its cost, and the connections that use it.
- Cost: AWS bills you directly, about $5 to $7 a month at last check. That is an estimate that can change.
For AI Agents
An AI agent can list your fixed addresses and read one (core.fixed_addresses.list, core.fixed_addresses.get, MCP tools fixed_addresses_list and fixed_addresses_get, level read) and ask for a check (core.fixed_addresses.check, MCP tool fixed_addresses_check, level write; it only marks the address due, and the check runs within a minute, at most one a minute). It never sees a key and never builds, uses, or releases an address: those are for people.
How It Stays Private
- Each fixed address is one server that carries your calls only. It holds only a public key; the matching private key is made inside your workspace and sealed there, so only your workspace can sign a call for the server.
- Nothing in AWS names your company, your account, or a connection: only a random name and the tag above.
- The AWS key is used only while building. When the address is ready, your workspace erases its copy.
