Job search
Cargo Review: Multiple Portfolio Sites Under One Subscription
Distinguish Cargo 3 sites, domain connections and collaborator permissions using completed multi-site planning examples.
Cargo 3’s subscription can support more than one portfolio site without charging a full subscription for every public cargo.site address. The important distinction is between sites, custom-domain connections and collaborators. Multiple sites do not automatically mean unlimited independently branded domains or separate accounts with identical billing rights.
This review checks Cargo’s public documentation and terms on October 21, 2026. No account was created, site edited or published, collaborator invited, domain connected or payment made. LandOffer publishes this review and offers job-search tools. Use recent job openings to decide whether separate portfolio destinations would help explain your work before creating more of them.

The multiple-site offer applies to Cargo 3
Cargo’s Rates & Services guide describes one or many public sites under a single account and unlimited public sites using cargo.site addresses. It lists $14 per month when billed yearly or $19 when billed monthly. That is the current Cargo 3 model assessed here, not an assumption about every historical Cargo product.
The distinction matters for older accounts. Cargo’s current guides explain that Cargo 2’s paid upgrade applies to a single site, whereas Cargo 3 uses the subscription model. The documentation also says Cargo 2 content cannot simply be imported into Cargo 3. Managing both in a workspace does not make them the same editor or establish a migration already completed.
For a job search, multiple sites could separate a principal portfolio from teaching notes or a distinct creative practice. They can also create extra maintenance. Give the second site a different reader task and a clear route back to the primary identity, rather than becoming another place to leave outdated project descriptions.
Unlimited public sites is a pricing description, not permission to publish confidential work. Nor is it a measured capacity, performance or availability test. This review did not build a large collection of sites or evaluate real loading behavior.
A custom-domain connection is not domain registration
A Cargo 3 subscription includes one custom-domain connection. Additional independent custom-domain connections are listed at $2 per month with yearly billing or $3 with monthly billing. Those amounts are connection charges, not the registration or renewal cost of buying each domain. Current rates
Cargo also documents a useful narrower rule: if a subscriber already uses a custom domain, connecting a subdomain of it to another Cargo site does not require an additional domain add-on. For example, a main portfolio and a notes site under the same domain family need not be priced like two unrelated domains. The actual domain must be controlled and configured appropriately; no DNS was inspected or changed for this review. Using subdomains
The current guides say externally registered domains can be connected without transferring registration to Cargo. Keep the external registrar renewal separate. A domain bought through Cargo also remains a separate item from the site subscription, according to its cancellation guidance.
Do not read “one free custom-domain connection” as a free domain for life. Before buying, record the subscription, any extra connection charge, each domain renewal and any optional commerce requirement. The public rates are US-dollar baselines; final billing and applicable charges were not checked in an account.
Worked example: route three sites without buying three subscriptions
Fictional creative frontend developer Avel has three planned destinations: a primary job-search portfolio, public teaching notes and an unfinished visual experiment. The portfolio needs a custom address. The notes need a recognizable relationship to the portfolio, while the experiment is not intended for public viewing. These are planning assumptions, not existing websites.
Avel completes a routing comparison using the documented prices:
| Address arrangement for the two intended public sites | Yearly-billing baseline | Completed decision |
|---|---|---|
Both use cargo.site addresses |
$14 × 12 = $168 subscription | Valid price baseline if no custom address is required |
Portfolio uses the included connection; notes use a cargo.site address |
$168 subscription | Meets the custom-portfolio requirement without another connection charge |
| Portfolio and notes use two independent custom domains | $168 + $2 × 12 = $192 | Adds $24 in annual connection charges, plus separate domain costs |
| Portfolio uses a custom domain; notes use its subdomain | $168 subscription under the documented subdomain rule | Selected arrangement to evaluate because the notes belong to the same identity |
The selected arrangement does not make registration free. Avel will keep the domain’s actual registrar bill in a separate record and confirm the intended connection before purchasing. The third experimental site is explicitly Private in the plan; he does not assume that leaving it unlinked will keep it private after subscription.
At monthly rates, the equivalent baseline with two independent custom-domain connections would be $19 + $3 = $22 per month before excluded costs. Twelve unchanged monthly payments would total $264, compared with the $192 yearly-billing model. These arithmetic comparisons model the documented billing arrangements, not a promise of unchanged future pricing or a tested checkout.
Avel’s completed choice is one subscription with one main custom-domain connection and a related subdomain for the notes, subject to confirmation of his setup. He rejects a separate domain for the notes because it solves no stated reader need. He also rejects publishing the experiment simply because another public site would have no additional base subscription charge.
The content remains distinct: the main portfolio explains his implementation decisions, while the notes teach a concept and credit any outside sources. Neither destination upgrades a tutorial exercise into production employment experience. Keep the same ownership and evidence boundaries when describing a project on more than one site.
Draft, preview, live and public are different states
Cargo’s editing guide says changes are saved as a draft without affecting the live version until published. Preview allows browsing within edit mode. A draft can persist while you work elsewhere, and publishing commits its changes to the live site.
Public availability requires a separate check. The guide says a subscription is required for sites to become public, with Private and password-protected options in Publish Settings. The current guides add that subscribing can make other sites in the account public under their cargo.site addresses unless explicitly Private. Check the public/private state of every site in the account before enabling a subscription rather than assuming a forgotten experiment is safely isolated.
“Save as new site” also deserves care: the editing guide says it publishes the draft on the new site. Do not treat it as an entirely inert local backup operation. This is a documented effect, not an action performed during the review.
Before sending an actual portfolio, inspect its intended public URL outside the editor and follow the project links. A preview can help review composition; it does not establish that a recruiter has the required access or that the public version contains your latest approved text. No reader-access check was executed on a candidate site here.
Collaboration is site access, not just another audience
The collaboration guide describes Admin, Editor and Viewer roles. Admin has full site access comparable to the primary owner. Editor can do most things but cannot invite users or change their permissions, manage domains, change the site name/Cargo URL, alter a site password or public/private status, receive contact-form emails or delete the site.
Viewer is intended for reviewing work in progress without editing. A Viewer can see a nonpublic site and unpublished changes in real time. That gives an authorized reviewer a way to inspect changes before publication, but it is broader exposure than simply giving someone the current public portfolio link.
Invitations are described as emails containing a site screenshot and join link. Consider the visible contents before inviting anyone, even if the purpose is feedback. Do not invite a reviewer to a site containing material they are not permitted to see. This review did not send an invitation or inspect how any role behaves in a private account.
Multiple sites under one subscription do not remove those boundaries. Keep the account owner, each site’s collaborators and the intended public audience separate in your planning. Do not share account credentials as a substitute for selecting a documented role.
Worked example: finish a review and publication responsibility record
Continue Avel’s fictional setup. A friend, Sena, will review the main portfolio’s draft explanation but should not edit or control it. Avel’s collaborator, Dario, may improve page text and layout on the teaching-notes site. Neither needs access to the unfinished experiment. All sharing permissions are stipulated and no invitation is sent.
| Person and site | Required task | Completed access decision |
|---|---|---|
| Sena, main portfolio | Read and comment on an unpublished explanation | Consider Viewer only after ensuring the entire visible draft is permitted for Sena |
| Dario, teaching notes | Edit approved text and layout | Consider Editor on that site, with an agreed publication process |
| Either person, visual experiment | No assigned task | Do not invite |
| Avel, all three sites | Maintain site states, addresses and final publication decisions | Retain owner responsibility; check the complete account’s site list before subscribing |
Avel also finishes a content-release record for the next portfolio revision. The current public version describes a personal prototype. The draft adds a diagram explaining a rendering decision. He must verify the diagram’s source, caption and contribution statement before publication; Sena’s view of the draft is not itself approval to make it public.
For Dario, the record says which text may change and that Avel will review the intended live version. This is a proposed working agreement, not a claim that Cargo enforces a custom approval workflow or that Editor is a draft-only role. The guide’s stated exclusions do not establish a mandatory owner sign-off for every publication.
Avel’s completed decision separates three events: an authorized person can view the draft; the correct content has been reviewed; and the owner has checked the intended public state. None is marked as an event already performed. Before real use, he would verify the actual role and publish behavior in the relevant site rather than relying on the table alone.

Renewal and cancellation need an account-level check
The public account guide places subscriptions, payments, domain names and invoices in Account Settings. The current help content says a subscription can be canceled there and that domains bought through Cargo renew annually as separate items. Canceling a site subscription does not by itself cancel those domain registrations. Current guides and billing questions
The terms say service cancellation takes effect immediately, can remove access and may lead to deletion of site information. They also state that Cargo does not have a refund policy and that domain purchases are non-refundable. Do not assume annual prepayment can always be refunded or cancellation merely disables a later renewal while preserving access.
The passages reviewed did not establish an exact universal site-subscription renewal charge date or a guaranteed preservation period after cancellation. Check the actual subscription record before acting. If you want to keep addresses usable in submitted applications, plan the destination and backups before ending service.
Keep a source archive instead of assuming an export
Cargo’s current guides explicitly say an export option is not offered. Keep original images, project text, captions, source diagrams, file links and an address-to-site record outside the builder. A local archive supports a later rebuild; it is not a portable copy of Cargo’s editing system or functioning site.
The same ownership discipline applies across multiple sites. Update a shared factual claim consistently, keep attributions with reused material and remove old public links deliberately. Choose the number of destinations you can keep accurate and current.
Cargo is worth evaluating when several distinct portfolio purposes fit one account and you understand the domain and collaboration costs. Start with a clear audience for each site, keep experiments explicitly private, and verify the live reading path before sharing. Continue matching the work you present to relevant opportunities through LandOffer, with the platform’s documented capabilities separate from untested hiring outcomes.


