1. LandOffer
  2. Blog
  3. All articles
  4. Authory vs. Journo Portfolio: Automatic Archiving or a Custom Work-Sample Site?

Job search

Authory vs. Journo Portfolio: Automatic Archiving or a Custom Work-Sample Site?

Two completed original incident-recovery and maintenance-brief decisions compare automated archives, custom portfolio sites, copy destinations, and the cost of staying live.

9 min readLandOffer team

Consider Authory when maintaining a searchable archive of published work is the main problem. Journo Portfolio is worth comparing when you want a custom work-sample website with article backups and other media. Both advertise automatic importing on relevant paid plans. The choice is not automation versus a purely manual site builder; it is which archive, presentation, and maintenance workflow fits your work.

This comparison uses public product descriptions and policies inspected on October 21, 2026. No account, import, backup, private link, export, or purchase was tested. LandOffer publishes this review and offers job-search tools. Start with the samples that support your target role; browse recent roles on LandOffer.ai if you need to define that target first.

A writer compares an organized publication archive with a curated work-sample booklet on a desk.

Compare the paid workflow you would actually use

Authory’s current pricing lists Free with 10 items and Lite with 50. Both are manually updated and list zero monitored sources. Lite costs $12 monthly or $9 per month billed yearly, totaling $108. Standard adds automatic importing of past and future work, unlimited items and monitored sources, custom-domain support, and audio/video uploads. It is $19 monthly or $15 per month billed yearly, totaling $180.

That makes Standard the first listed Authory plan for ongoing source monitoring. Buying Lite because it has backups does not buy automatic discovery. Professional adds integrations and larger-media support, but a candidate who only needs the Standard workflow should identify a specific missing requirement before paying for it.

Journo Portfolio’s current pricing lists Plus at $9 monthly or $7 per month billed annually, totaling $84, for publication on its subdomain. Pro is $12 monthly or $10 billed annually, totaling $120, and its current card includes automatic article import, article backups, privacy features, a custom domain, and 120 minutes of video/audio upload allowance. The page says ten audio minutes count as one video minute toward that allowance.

Journo’s current billing guide distinguishes its new Free editor from a published portfolio: new Free sites remain unpublished until a paid upgrade. It says there is no longer a seven-day trial for new accounts. Older Free accounts can have different inherited limits. Do not use an old free-site recommendation as a promise about a new account.

Automatic importing still has a presentation step

Authory’s source tutorial describes monitoring eligible sources for future bylined articles, podcast episodes, or channel videos. Its separate auto-updating portfolio guide explains that imported items enter the archive; collection filters and auto-update rules determine whether matching items appear in a displayed collection.

Check source monitoring separately from the collection rules that determine what becomes public. Authory also directs work without a byline toward manual addition. A branded documentation page, collaborative project, or ghostwritten article should not be assumed discoverable through your name.

Journo’s current Pro card also advertises automatic article import. Its item guide describes URL imports, file uploads, and original blog items, and distinguishes adding items from assigning them to article or gallery blocks. That is enough to reject the idea that Journo is manual-only. It does not establish identical discovery coverage, supported sources, import latency, or missed-item recovery across the two products.

The relevant question is which recurring work remains yours: checking completeness, correcting titles and credit, selecting what belongs in the job-search view, and checking destination links. A frequently updated archive and a carefully curated application portfolio can serve different purposes even when they contain some of the same articles.

Worked asset: a completed disappearance-and-recovery record

Here is an original fictional incident record for Devon, a developer educator. Devon has one approved public tutorial called “Debugging a Queue Worker.” A publisher moves that tutorial during a redesign. The incident and tutorial are fictional. No publisher outage, captured backup, or recovery operation was tested for this comparison.

Devon’s acceptance condition is specific: a visitor must reach an approved, readable sample that preserves its title, publication date, attribution, and code formatting. A saved thumbnail would not meet Devon’s stated requirement. The incident record is completed as follows:

Scenario state Completed decision What would have to be verified in an account
Before the move Keep the original URL, title, date, and approved source files in an independent local record. Whether an actual full backup exists and renders the relevant content.
Original URL stops resolving Pause use of that destination in the application portfolio; do not assume monitoring repaired it. Whether the publisher supplied a replacement URL, and whether an existing backup is readable.
Publisher supplies an approved replacement Prefer the new original destination after checking it against the sample record. Final visitor destination, attribution, code blocks, and absence of unrelated content.
No replacement is available Consider a saved copy only if the existing permission covers this sharing route. Otherwise use a different approved sample. Backup completeness and the exact access and click behavior.

For Authory, the documented repair option is its sharing setting: a portfolio item can link to a copy instead of the original. A source-wide change could affect every item attached to that source, so Devon’s proposed repair is limited to the affected sample. The archive’s existence alone is not evidence that this visitor route has been enabled.

For Journo, the published backup guidance describes article PDF and image backups and selecting a PDF when an original article disappears. Devon would inspect the actual PDF before routing a visitor to it. A PDF that omits a crucial diagram or clips a code block fails Devon’s acceptance condition even if the backup operation itself completed.

Devon’s finished incident decision is therefore replacement original first; inspected, permission-cleared saved copy second; another approved sample if neither works. Neither product can recover content it never captured merely because a subscription is active. This review has not established that either captured Devon’s fictional tutorial.

Devon’s closure note makes the next review easier: “Record the new destination and the version inspected; retain the previous URL for provenance. Do not describe the repaired sample as a live runnable project.” That separates a useful writing sample from the source repository or environment needed to reproduce its code.

A candidate reviews a maintenance calendar beside separate archive and presentation folders resting on the desk.

Saved copies and private sharing need separate review

Authory’s older ownership statement describes full backups as private and says an archive can be exported as XML or HTML on request. Its sharing guide dated September 17, 2026 explicitly describes making a saved copy available through item, source, or collection settings. Read those together: a default-private backup is not a promise that it can never be shared through the product.

The current pricing table lists password protection and secret links on paid Authory plans, but these do not provide permission to republish a publisher’s or employer’s material. A source-wide setting also deserves particular care when some items can be shared as copies and others cannot.

Journo Pro advertises passwords and the public privacy guidance describes secure-link access. These are sharing controls, not proof of the recipient’s identity or a restriction on everything they might copy after access. Exclusion from search results is also different from an access barrier. Keep confidential or unapproved source material outside the portfolio rather than relying on a hidden URL to resolve a rights problem.

The backup artifacts have different limits from editable originals. Journo’s PDF export guide describes choosing articles and ordering blocks for a PDF. A printable collection is not a working copy of your website, Markdown repository, build tools, or interactive demo. Authory’s XML/HTML export is described as a request-based service, not an export that we executed or a tested migration into another builder.

Worked asset: a completed maintenance-and-site brief

A second fictional candidate, Elise, is applying for developer-education roles. She has 24 public articles, two short demonstration videos, and one original tutorial outline. She expects further public articles but wants an application site that foregrounds two teaching case studies instead of presenting every new item equally.

Her completed comparison uses the same four requirements for both products:

Requirement in Elise’s brief Authory Standard fit Journo Pro fit
Keep future public writing discoverable Source monitoring is explicitly listed; eligible source and byline coverage still need checking. Automatic article import is listed; actual source coverage and timing remain untested.
Present two teaching cases with context Collections and About Pages can organize selected material. Custom pages and article/gallery blocks can support the planned site structure.
Preserve readable writing if a publisher changes Searchable backups and configurable copy destinations are described. Article backups and PDF/image recovery routes are described.
Keep an independent working copy Request-based XML/HTML is an additional export route, not a replacement for original files. PDF export is an additional presentation artifact, not editable tutorial source.

Elise writes the site brief before choosing a template: Home will explain her teaching focus; two case pages will each show the learner problem, her contribution, a selected article, and a short demo; an archive page will hold broader writing. Elise labels the original tutorial outline as unpublished and keeps its status separate from the 24 public articles. Nothing in the brief grants permission to attach someone else’s name or a publisher’s endorsement to it.

Her completed maintenance rule is equally concrete: review new arrivals for attribution and relevance before placing them in the two featured cases; check those case destinations before each application; keep a separate local folder of approved text, images, and demo sources. Automation can populate a broader archive without determining which work best supports a particular application.

Elise provisionally prefers Journo Pro for this custom site brief, with automatic import as an advertised feature to verify rather than assume absent. A different brief centered on a searchable cross-publication archive and source-level management could favor Authory Standard. The decision compares the required work, not an unmeasured claim that one saves more hours.

Compare annual commitments and the cost of staying live

At the observed annual figures, Authory Standard is $180 and Journo Pro is $120, a $60 difference for one full year. At the observed monthly rates, six months would be $114 and $72 respectively. These totals compare the displayed prices under unchanged-rate assumptions. Coverage, purchase conditions, future prices, and the value of a particular application remain separate questions.

Authory’s pricing table limits its included domain to 12 months on qualifying annual plans. Journo’s current Pro pricing says registration, renewals, and transfers are included, rather than only the first year. Its domain guidance distinguishes a managed domain from one you keep with an external registrar. An external registration can still have its own bill, and changing a registered domain can have an additional cost. Included hosting does not settle every domain or email expense.

Journo’s current billing guide says paid features remain until the billing period ends after cancellation; then the public site is unpublished while content stays in the editor. Its cancellation policy, dated March 13, 2022 and still linked publicly, lists a refund-request window of 14 days after subscribing or seven days after renewal, with $10 deducted if a domain was registered or renewed. Review the specific purchase terms instead of equating retained editor content with a live application link.

Authory currently advertises a 14-day trial without a card and a continuing Free option. Its pricing differentiates that Free plan from Standard’s monitoring and unlimited items. Do not assume a downgrade preserves every paid feature or automatically keeps an unlimited archive and custom-domain site functioning the same way. Confirm the actual account transition and export needs before changing plans.

Choose around the failure you need to prevent: losing track of published work, losing a readable sample, or sending a recruiter to a poorly organized page. Both tools can participate in that workflow, but neither supplies rights clearance, verified import completeness, or a job outcome. Keep the portfolio brief tied to real opportunities by browsing recent roles on LandOffer.ai.

Sources and Further Reading