{"id":3704,"date":"2026-11-14T15:00:00","date_gmt":"2026-11-14T07:00:00","guid":{"rendered":"https:\/\/www.olares.com\/articles\/?p=3704"},"modified":"2026-11-10T13:10:51","modified_gmt":"2026-11-10T05:10:51","slug":"recovery-plan-solo-business-self-hosted-accounts","status":"publish","type":"post","link":"https:\/\/www.olares.com\/articles\/recovery-plan-solo-business-self-hosted-accounts\/","title":{"rendered":"A Recovery Plan for a Solo Business With Self-Hosted Accounts"},"content":{"rendered":"

A solo business can prepare for losing its only admin device in two steps. First, map which identity, factor, and device unlocks each service. Then make sure each critical service has at least one documented recovery route that still works without that device and without the account it is meant to recover.<\/p>\n

Good self-hosted account recovery is built before anything goes missing. The examples below show how real providers set conditions on recovery. Each service you run still needs its own documented route on your map.<\/p>\n

Build a service-by-service identity map<\/h2>\n

Start with one row for each service your business depends on. Each row links the account to the identity that signs in, the factors that prove it, and the route that brings it back.<\/p>\n

Record the identity and factor chain<\/h3>\n

Use the same row template for every service, so gaps stand out:<\/p>\n

    \n
  1. Service:<\/strong> the app, console, or system you administer.<\/li>\n
  2. Sign-in identity:<\/strong> the exact username, email, or ID used to log in as admin.<\/li>\n
  3. Password or identity provider:<\/strong> whether login depends on another account, such as a single sign-on provider.<\/li>\n
  4. Second factors and where they live:<\/strong> authenticator app, security key, or passkey, and which device holds each one.<\/li>\n
  5. Recovery contact:<\/strong> the backup email or phone, plus the account or device that controls it.<\/li>\n
  6. Proof authority:<\/strong> domain or DNS control, or another ownership check, but only where that service’s documented route uses it.<\/li>\n
  7. Documented route:<\/strong> the service’s own recovery steps and their prerequisites.<\/li>\n<\/ol>\n

    Then mark each dependency as “on the admin device,” “in a separate account,” or “held offline.” The service account and the thing that can recover it are separate entries. Keep them that way.<\/p>\n

    Treat provider examples as examples, not a full stack<\/h3>\n

    Two named services show how much a route can depend on. Google Workspace administrator recovery<\/a> can use a configured recovery email or phone. Without those, its recovery wizard asks you to verify your domain by adding a DNS record, and support-assisted recovery comes only after automated recovery, with proof of domain ownership. Cloudflare’s route<\/a> for losing all 2FA devices and backup codes needs access to the account email and a device you have logged in from before.<\/p>\n

    Neither example tells you how a locally administered app recovers its admin. Olares is one case. Our documentation separates LarePass (the client app), the Olares ID (your identity), and the Olares server environment. It describes a 12-word mnemonic as the material for recovering the Olares ID. Write those down as three separate rows. For the access side, follow our Olares access recovery guide<\/a> instead of assuming the mnemonic covers everything.<\/p>\n

    Test each recovery path for independence<\/h2>\n

    A route counts as independent only when every identity, factor, inbox, device, and recovery authority it needs is still reachable without the lost device and the locked account. If even one is out of reach, the route is conditional or unavailable for this scenario.<\/p>\n

    \"Decision
    Decision diagram for checking whether every recovery prerequisite is reachable without the lost device or the locked account.<\/figcaption><\/figure>\n

    Go down your map and ask one question per prerequisite: can I reach this from a different device, without signing in to the account I’m trying to recover? A backup email counts only if you can open that inbox elsewhere. If its only signed-in session lives on the lost phone, the route loops back to what you lost.<\/p>\n

    The provider examples show where this test catches problems. For Google Workspace, the DNS route works only if you can still sign in to your domain host. If that login also needs the lost device, mark the route conditional. Google also lets another super administrator generate backup codes<\/a> for a locked admin. A one-person business usually has no second admin, so leave that route off your map unless one actually exists.<\/p>\n

    Cloudflare’s fallback is the clearest failure point. It checks whether you are using a device that has logged in before. If the lost device was the only one, that check may fail. Cloudflare notes that clearing cookies or switching IP addresses can also make a device unrecognizable. Manual verification may be available after a failed device check, but it is a possible next step, not promised access.<\/p>\n

    Record provider verification on your map as a boundary: the point where recovery moves out of your hands. For Olares, getting your identity back is one row on the map, not proof that server administration is restored. Keep the admin access route as its own entry.<\/p>\n

    Store recovery materials outside the dependency chain<\/h2>\n

    Keep the recovery materials each service officially provides somewhere you can reach without the admin device and without the account they recover. Then check that the storage itself does not quietly bring back the same dependency.<\/p>\n

    Use only what each service documents. Google Workspace advises admins<\/a> to enroll more than one security key, keep the spare in a safe place, and store backup codes securely. Cloudflare recommends several security keys<\/a> and lets you download, print, or copy backup codes to a secure location. Each Cloudflare backup code works only once. Mark a used code as consumed and keep the unused codes securely. If you generate a new set, update your stored copy and follow the provider\u2019s invalidation rules for the old set.<\/p>\n

    Our documentation describes the Olares ID mnemonic<\/a> as something you keep offline. Never put the words in screenshots, notes apps, or shared documents. Having the mnemonic restores the identity, not necessarily your full admin access.<\/p>\n

    Here is the check to run on any storage you choose. An encrypted file or password manager vault counts as independent only if you can unlock it without the lost device or the locked account. A printed sheet in a secure place you can physically reach avoids that problem, but it has to be kept current. Think of this as a planning approach, not a tested universal method. Each service’s own rules still apply.<\/p>\n

    After device loss, follow the service’s documented route<\/h2>\n

    Once the device is gone, work from the map, not from memory. Follow each service’s own steps, and stop treating recovery as self-service once it reaches provider verification.<\/p>\n

      \n
    1. Find the affected services.<\/strong> Mark every row whose sign-in, factor, or recovery contact depended on the lost device.<\/li>\n
    2. Check the prerequisites.<\/strong> For each route, confirm that the inbox, spare key, backup codes, domain host login, or other authority is reachable right now from a different device.<\/li>\n
    3. Use your independent materials first.<\/strong> Spare keys and stored backup codes are the most direct path where a service accepts them.<\/li>\n
    4. Follow only that service’s instructions.<\/strong> For Google Workspace, use configured recovery options. Try the DNS route only if you control the domain host, and move to support-assisted recovery only after automated recovery fails. For Cloudflare, if 2FA and codes are both gone, the fallback needs the account email and a previously used device. A verified device leads to emailed instructions within 3 to 5 days, and Cloudflare says that wait cannot be expedited.<\/li>\n
    5. Stop at the provider boundary.<\/strong> Ownership checks, manual verification, and support review are up to the provider. Gather the requested proof and wait for their response.<\/li>\n
    6. Mark gaps honestly.<\/strong> If a self-hosted service has no verified route on your map, mark it unavailable. Use only that service’s current recovery instructions, and never borrow another provider’s steps.<\/li>\n<\/ol>\n

      Treat account recovery, data restoration, and device rebuilding separately<\/h2>\n

      Getting back into an account, restoring backed-up data, and rebuilding a lost device are three separate outcomes. The recovery routes above deal only with authentication and account access.<\/p>\n

      Signing back in does not bring back files that were only stored on the lost device. It does not recreate the admin setup you had on it, either. Plan data restoration around your backups and their own restore instructions, and set up a replacement device as a separate task. Keeping these on separate lists stops you from treating a successful login as full recovery.<\/p>\n

      FAQs<\/h2>\n

      Should a solo business add a second administrator?<\/h3>\n

      Some providers build recovery around a second admin. Google Workspace, for example, lets a super administrator generate backup codes for another locked admin. That helps only if the second admin is a real, reachable person or account you actually control from somewhere other than the lost device. If you can’t set one up safely, don’t count it in your plan.<\/p>\n

      Does a password manager solve the lost-device problem?<\/h3>\n

      Only if you can unlock it without the lost device. If the vault’s master password, second factor, or only synced session depends on that device, the vault is part of the same chain. Check its own unlock route the same way you check every other service.<\/p>\n

      How often should the recovery map be updated?<\/h3>\n

      Update it whenever something on it changes: a new service, a new phone or security key, a changed recovery email, a domain host move, or used backup codes. Cloudflare codes work only once, for example, so using one means your stored set is no longer complete.<\/p>\n","protected":false},"excerpt":{"rendered":"

      A solo business can prepare for losing its only admin device in two steps. First, map which identity, factor, and device unlocks each service. Then make sure each critical service has at least one documented recovery route that still works without that device and without the account it is meant to recover. Good self-hosted account […]<\/p>\n","protected":false},"author":3,"featured_media":3702,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3704","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":8}},"yoast_head":"\nA Recovery Plan for a Solo Business's Admin Accounts<\/title>\n<meta name=\"description\" content=\"Map which identity, factor, and device unlocks each service, test each recovery path for independence, and store recovery materials outside that chain.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"A Recovery Plan for a Solo Business's Admin Accounts\" \/>\n<meta property=\"og:description\" content=\"Map which identity, factor, and device unlocks each service, test each recovery path for independence, and store recovery materials outside that chain.\" \/>\n<meta property=\"og:url\" content=\"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/\" \/>\n<meta property=\"og:site_name\" content=\"Olares Articles\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/people\/Olares\/61579156063357\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-14T07:00:00+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/43.166.210.66:8080\/wp-content\/uploads\/2026\/11\/recovery-plan-solo-business-self-hosted-accounts-featured.png\" \/>\n\t<meta property=\"og:image:width\" content=\"654\" \/>\n\t<meta property=\"og:image:height\" content=\"436\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Yajing Wang\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Olares_OS\" \/>\n<meta name=\"twitter:site\" content=\"@Olares_OS\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Yajing Wang\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/#article\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/\"},\"author\":{\"name\":\"Yajing Wang\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#\\\/schema\\\/person\\\/d106d6ed3db3314a7a18162f8b4c27ae\"},\"headline\":\"A Recovery Plan for a Solo Business With Self-Hosted Accounts\",\"datePublished\":\"2026-11-14T07:00:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/\"},\"wordCount\":1513,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#organization\"},\"image\":{\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/recovery-plan-solo-business-self-hosted-accounts-featured.png\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/\",\"url\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/\",\"name\":\"A Recovery Plan for a Solo Business's Admin Accounts\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/#primaryimage\"},\"image\":{\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/recovery-plan-solo-business-self-hosted-accounts-featured.png\",\"datePublished\":\"2026-11-14T07:00:00+00:00\",\"description\":\"Map which identity, factor, and device unlocks each service, test each recovery path for independence, and store recovery materials outside that chain.\",\"breadcrumb\":{\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/recovery-plan-solo-business-self-hosted-accounts-featured.png\",\"contentUrl\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/recovery-plan-solo-business-self-hosted-accounts-featured.png\",\"width\":654,\"height\":436,\"caption\":\"A solo business owner writes service recovery dependencies on a paper map beside a spare security key.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\\\/\\\/43.166.210.66:8080\\\/recovery-plan-solo-business-self-hosted-accounts\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"A Recovery Plan for a Solo Business With Self-Hosted Accounts\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#website\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/\",\"name\":\"Olares Articles\",\"description\":\"Perspectives on private AI, self-hosting, and a digital life you control.\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#organization\",\"name\":\"Olares\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/mascot_black.png\",\"contentUrl\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/mascot_black.png\",\"width\":1000,\"height\":1000,\"caption\":\"Olares\"},\"image\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/people\\\/Olares\\\/61579156063357\\\/\",\"https:\\\/\\\/x.com\\\/Olares_OS\",\"https:\\\/\\\/github.com\\\/beclab\\\/Olares\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/olarestech\\\/\",\"https:\\\/\\\/www.youtube.com\\\/@OlaresOS\\\/featured\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#\\\/schema\\\/person\\\/d106d6ed3db3314a7a18162f8b4c27ae\",\"name\":\"Yajing Wang\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g\",\"caption\":\"Yajing Wang\"},\"description\":\"Yajing Wang is Head of Growth at Olares. Yajing's work focuses on helping people understand personal cloud software, local AI, and self-hosted applications, with an emphasis on clear explanations of how these tools fit into everyday workflows.\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/author\\\/yajing-wang\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"A Recovery Plan for a Solo Business's Admin Accounts","description":"Map which identity, factor, and device unlocks each service, test each recovery path for independence, and store recovery materials outside that chain.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/","og_locale":"en_US","og_type":"article","og_title":"A Recovery Plan for a Solo Business's Admin Accounts","og_description":"Map which identity, factor, and device unlocks each service, test each recovery path for independence, and store recovery materials outside that chain.","og_url":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/","og_site_name":"Olares Articles","article_publisher":"https:\/\/www.facebook.com\/people\/Olares\/61579156063357\/","article_published_time":"2026-11-14T07:00:00+00:00","og_image":[{"width":654,"height":436,"url":"http:\/\/43.166.210.66:8080\/wp-content\/uploads\/2026\/11\/recovery-plan-solo-business-self-hosted-accounts-featured.png","type":"image\/png"}],"author":"Yajing Wang","twitter_card":"summary_large_image","twitter_creator":"@Olares_OS","twitter_site":"@Olares_OS","twitter_misc":{"Written by":"Yajing Wang","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/#article","isPartOf":{"@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/"},"author":{"name":"Yajing Wang","@id":"https:\/\/www.olares.com\/articles\/#\/schema\/person\/d106d6ed3db3314a7a18162f8b4c27ae"},"headline":"A Recovery Plan for a Solo Business With Self-Hosted Accounts","datePublished":"2026-11-14T07:00:00+00:00","mainEntityOfPage":{"@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/"},"wordCount":1513,"commentCount":0,"publisher":{"@id":"https:\/\/www.olares.com\/articles\/#organization"},"image":{"@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/#primaryimage"},"thumbnailUrl":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/11\/recovery-plan-solo-business-self-hosted-accounts-featured.png","inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/","url":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/","name":"A Recovery Plan for a Solo Business's Admin Accounts","isPartOf":{"@id":"https:\/\/www.olares.com\/articles\/#website"},"primaryImageOfPage":{"@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/#primaryimage"},"image":{"@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/#primaryimage"},"thumbnailUrl":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/11\/recovery-plan-solo-business-self-hosted-accounts-featured.png","datePublished":"2026-11-14T07:00:00+00:00","description":"Map which identity, factor, and device unlocks each service, test each recovery path for independence, and store recovery materials outside that chain.","breadcrumb":{"@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/#primaryimage","url":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/11\/recovery-plan-solo-business-self-hosted-accounts-featured.png","contentUrl":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/11\/recovery-plan-solo-business-self-hosted-accounts-featured.png","width":654,"height":436,"caption":"A solo business owner writes service recovery dependencies on a paper map beside a spare security key."},{"@type":"BreadcrumbList","@id":"http:\/\/43.166.210.66:8080\/recovery-plan-solo-business-self-hosted-accounts\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.olares.com\/articles\/"},{"@type":"ListItem","position":2,"name":"A Recovery Plan for a Solo Business With Self-Hosted Accounts"}]},{"@type":"WebSite","@id":"https:\/\/www.olares.com\/articles\/#website","url":"https:\/\/www.olares.com\/articles\/","name":"Olares Articles","description":"Perspectives on private AI, self-hosting, and a digital life you control.","publisher":{"@id":"https:\/\/www.olares.com\/articles\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.olares.com\/articles\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.olares.com\/articles\/#organization","name":"Olares","url":"https:\/\/www.olares.com\/articles\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.olares.com\/articles\/#\/schema\/logo\/image\/","url":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/09\/mascot_black.png","contentUrl":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/09\/mascot_black.png","width":1000,"height":1000,"caption":"Olares"},"image":{"@id":"https:\/\/www.olares.com\/articles\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/people\/Olares\/61579156063357\/","https:\/\/x.com\/Olares_OS","https:\/\/github.com\/beclab\/Olares","https:\/\/www.linkedin.com\/company\/olarestech\/","https:\/\/www.youtube.com\/@OlaresOS\/featured"]},{"@type":"Person","@id":"https:\/\/www.olares.com\/articles\/#\/schema\/person\/d106d6ed3db3314a7a18162f8b4c27ae","name":"Yajing Wang","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g","caption":"Yajing Wang"},"description":"Yajing Wang is Head of Growth at Olares. Yajing's work focuses on helping people understand personal cloud software, local AI, and self-hosted applications, with an emphasis on clear explanations of how these tools fit into everyday workflows.","url":"https:\/\/www.olares.com\/articles\/author\/yajing-wang\/"}]}},"_links":{"self":[{"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/posts\/3704","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/comments?post=3704"}],"version-history":[{"count":2,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/posts\/3704\/revisions"}],"predecessor-version":[{"id":3762,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/posts\/3704\/revisions\/3762"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/media\/3702"}],"wp:attachment":[{"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/media?parent=3704"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/categories?post=3704"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/tags?post=3704"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}