What “unlimited websites” should mean in an Astrina plan

“Unlimited” sounds simple. It rarely is. In an Astrina plan, the first question is what the limit applies to: active sites, published sites, parked domains, test environments, or account-level usage.

A team with 12 live sites may hear “unlimited” and assume every connected domain is covered. That may be true, or it may not be. Ask whether the plan counts each website, each domain, each property, or each tracked environment. Those are not the same thing.

Here is the practical test: if your team can spin up three staging sites this week, retire two next month, and launch four new brand pages in Q4, the wording matters. One plan might treat all 9 as free. Another might allow unlimited sites but still cap traffic or seats.

Ask for the definition in writing. A short sentence from Astrina support can save a long billing argument later.

When unlimited-site pricing is the right fit

Unlimited-site pricing fits teams that change shape often. Agencies do this all the time. A client comes in, a client leaves, and the site count jumps from 18 to 22 before the month ends.

It also works well for internal marketing groups that launch many campaign microsites. One quarter can bring 6 landing pages. The next quarter can bring 1. A per-site model makes that swing visible on every invoice.

There is a simpler reason too. Some teams dislike re-checking the bill every time a new site goes live. If the price stays stable while the portfolio changes, planning gets easier. Finance likes that. So does anyone who has to approve the purchase.

Unlimited-site pricing can also fit companies with frequent acquisitions. One brand becomes three, then five. The question stops being “how many websites do we have?” and becomes “how fast can we connect them?”

Limits that can still apply even on an unlimited plan

“Unlimited” is often a scope word, not a promise without boundaries. A plan can still have traffic thresholds, seat limits, storage caps, or support rules.

Traffic is the obvious one. A plan may permit unlimited websites while still expecting use to stay within a certain volume band. Seats matter too. If only 2 users are included, the fourth analyst may need an add-on.

Storage can be another quiet constraint. Logs, exports, and retained history all take space. If your team keeps 12 months of data, ask whether that is included or billed separately.

Implementation rules matter as well. Some plans include self-serve setup only. Others cover guided onboarding or migration support, and some do not. One sentence in the contract can change the whole deal.

Support scope is easy to overlook. Does “unlimited” mean unlimited websites with standard email support, or does it include a named contact? That detail matters when 30 sites go live in one week.

How to compare unlimited pricing against per-site pricing

Start with math, not slogans. Take your current site count, then add the next 12 months of launches, acquisitions, and temporary campaign sites. If that number reaches 14, a per-site model may already be more expensive than it looks.

Now look at volatility. A plan priced per site can be cheap at 3 sites and costly at 13. Unlimited-site pricing can remove that step function. That is useful if your count changes every quarter.

Compare the cost of churn as well. If one brand closes and another opens, do you pay twice? A per-site model may bill both transitions. A broader unlimited plan may absorb them.

There is a second question: how much administrative work does each model create? If billing review takes 2 hours every month because sites keep changing, that labor has a cost. It is not printed on the invoice, but it still exists.

Use a simple table before you decide.

Questions to ask before choosing unlimited

Ask about renewals first. Is the price fixed for 12 months, or can it change at renewal? A plan that looks generous in month 1 can feel different in month 13.

Then ask about fair-use language. Some contracts say “unlimited” but still reserve the right to address unusual usage. That is normal in software contracts, but you should know what “unusual” means before you sign.

Ask what happens if your usage pattern changes. If you move from 8 sites to 80, does the plan still fit? If traffic rises sharply, does Astrina ask for a new tier? Put the answer on paper.

Do not skip the question about included support. If the plan covers unlimited websites but only 1 onboarding session, that affects rollout timing. A product can be affordable and still cost time.

One more thing. Ask whether subdomains count separately. Many teams forget this until launch week.

What to include in an unlimited pricing request to Astrina

Keep the request short, but not vague. Astrina can answer faster if you include the number of sites you expect now, the number you expect in 6 to 12 months, and whether those sites are live, staging, or planned.

Include your site types. A news site, a campaign microsite, and a documentation portal may have very different tracking needs. If there are 4 departments or 3 brands involved, say so.

List the people who will use the account. If 2 analysts and 5 marketers need access, mention both groups. Seats can affect the right plan.

Say whether you need onboarding help or migration support. If you are moving from another tool, include that too. If you are planning how to migrate website analytics, that context helps Astrina understand setup time and implementation effort.

End with one direct question: “Does Astrina pricing for unlimited websites fit our current and expected setup, and what limitations still apply?” That sentence is plain, and plain is useful.

Common situations where unlimited websites still need a custom quote

Agencies often need a custom quote. A standard self-serve plan may not cover the way an agency manages 25 client sites, different owners, and separate billing needs. The site count is only part of the story.

Resellers also need more detail. If one account contains 40 customer properties, but each customer needs different permissions, you are no longer asking a simple pricing question. You are asking for account structure, support scope, and probably procurement terms.

Multi-brand operators can run into the same issue. A parent company may control 8 consumer brands, 3 regional sites, and a handful of campaign domains. The total is not the problem. The relationship between those sites is the problem.

Platform teams can trigger custom review too. If they want to provision sites automatically through internal tools, the implementation rules may need adjustment. That is rarely a stock-plan conversation.

There is another common case: teams with strict finance controls. If one department pays for 5 sites and another pays for 6, the standard package may not map cleanly to the ledger. A custom quote can make the paperwork less awkward.

How to compare unlimited pricing against per-site pricing

If you are still deciding, compare 3 numbers: your current site count, your projected site count in 12 months, and the cost of a billing mistake. That last one is often ignored.

Ask a practical question. If the count grows from 5 to 15, does the per-site model rise linearly or jump in tiers? If the jump is large, unlimited pricing may be simpler even when it is not the cheapest line on day 1.

Look at ownership changes too. Teams often add and remove sites in bursts. A per-site plan can feel fair until six sites are added in one sprint. Then fairness looks expensive.

There is no prize for choosing the most complex pricing model. Choose the one that matches the rhythm of your work. If your rhythm is monthly launches, use that fact.

Next step: confirm the unlimited definition and request the right pricing

Before you ask for a quote, define “unlimited” in your own words. Write down whether you mean unlimited active sites, unlimited domains, or unlimited environments. Use one sentence. Then send it to Astrina.

If you want a faster answer, include 4 details: current site count, expected site growth, number of users, and any migration or onboarding needs. That is enough for most initial replies.

Ask Astrina to confirm the limit that matters most to you. For some teams it is traffic. For others it is seats or support. For others, it is the number of client accounts under one login.

Then wait for the part that matters: the written definition. That is the line that decides whether “unlimited” really means unlimited for your team, or only unlimited within a narrower box.