--- title: 1Password and ngrok in Practice | daily.dev description: An ngrok user shares a hands-on walkthrough of the 1Password ngrok shell plugin, which stores ngrok authtokens in a 1Password vault instead of a local... canonical: https://daily.dev/posts/1password-and-ngrok-in-practice-7x0gje4jt twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: 1Password and ngrok in Practice | daily.dev og:description: An ngrok user shares a hands-on walkthrough of the 1Password ngrok shell plugin, which stores ngrok authtokens in a 1Password vault instead of a local... og:url: https://daily.dev/posts/1password-and-ngrok-in-practice-7x0gje4jt og:image: https://api.daily.dev/og/posts/7X0Gje4JT.png og:image:alt: 1Password and ngrok in Practice og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # 1Password and ngrok in Practice **[ngrok Blog](https://daily.dev/sources/ngrok)** · 4 min read · 0 upvotes · 0 comments ## Summary An ngrok user shares a hands-on walkthrough of the 1Password ngrok shell plugin, which stores ngrok authtokens in a 1Password vault instead of a local ngrok.yml file. Setting up the plugin involves installing the 1Password app and CLI, connecting them, and choosing a scope: prompt on each shell, per-directory default, or global default. Once configured, running ngrok http triggers a 1Password authentication step that loads the correct token into memory, keeping credentials synchronized across machines and safer during demos. Teams and Business accounts can also centrally issue and manage ngrok credentials via 1Password without users logging into the ngrok dashboard. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I avoid putting my ngrok authtoken in plaintext in ngrok.yml? Use the 1Password ngrok shell plugin, which stores authtokens in a 1Password vault instead of a local ngrok.yml file. When you run a command like ngrok http 80, the plugin authenticates against your vault and loads the correct authtoken into memory, so credentials never sit exposed in a config file or on screen during demos. _Developers hardening their local credential setup can find integration walkthroughs like this on daily.dev._ ### How can I keep ngrok credentials separate between multiple projects on the same machine? Configure the 1Password ngrok shell plugin to automatically use a specific credential for a given directory and its subdirectories. This per-directory scoping keeps each project's ngrok authtoken isolated, preventing accidental token resets or mix-ups when switching between projects on one machine. _daily.dev surfaces practical setups like this for engineers juggling multiple project credentials._ ### Can a team manage ngrok credentials centrally without giving everyone dashboard access? Yes, with a 1Password Teams or Business account paired with the ngrok shell plugin, credentials can be issued and managed centrally by team, project, or individual, and team members never need to log into the ngrok dashboard directly to get their authtoken. _Teams standardizing credential workflows can track integrations like this via daily.dev._ ## Similar posts on daily.dev - [Self-hosted HTTP tunnels with SSH and nginx](https://daily.dev/posts/self-hosted-http-tunnels-with-ssh-and-nginx-qeu3pqxry) · Lobsters · 1 upvotes · 0 comments --- Tags: [#devtools](https://daily.dev/tags/devtools), [#cli](https://daily.dev/tags/cli), [#secrets-management](https://daily.dev/tags/secrets-management) [View this post on daily.dev](https://daily.dev/posts/1password-and-ngrok-in-practice-7x0gje4jt) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"1Password and ngrok in Practice","url":"https://daily.dev/posts/1password-and-ngrok-in-practice-7x0gje4jt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/1password-and-ngrok-in-practice-7x0gje4jt"},"datePublished":"2026-08-23T07:21:00.100Z","dateModified":"2026-08-23T07:28:52.467Z","description":"An ngrok user shares a hands-on walkthrough of the 1Password ngrok shell plugin, which stores ngrok authtokens in a 1Password vault instead of a local...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/790e827e7b5d39eb4ed39d292fbf534f?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/790e827e7b5d39eb4ed39d292fbf534f?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ngrok Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ngrok Blog","logo":"https://media.daily.dev/image/upload/s--718XXxvE--/f_auto,q_auto/v1787469610/logos/ngrok?_a=BAMAMicg0","url":"https://daily.dev/sources/ngrok"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/1password-and-ngrok-in-practice-7x0gje4jt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devtools,cli,secrets-management","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ngrok Blog","item":"https://daily.dev/sources/ngrok"},{"@type":"ListItem","position":3,"name":"1Password and ngrok in Practice"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/1password-and-ngrok-in-practice-7x0gje4jt#faq","mainEntity":[{"@type":"Question","name":"How do I avoid putting my ngrok authtoken in plaintext in ngrok.yml?","acceptedAnswer":{"@type":"Answer","text":"Use the 1Password ngrok shell plugin, which stores authtokens in a 1Password vault instead of a local ngrok.yml file. When you run a command like ngrok http 80, the plugin authenticates against your vault and loads the correct authtoken into memory, so credentials never sit exposed in a config file or on screen during demos. Developers hardening their local credential setup can find integration walkthroughs like this on daily.dev."}},{"@type":"Question","name":"How can I keep ngrok credentials separate between multiple projects on the same machine?","acceptedAnswer":{"@type":"Answer","text":"Configure the 1Password ngrok shell plugin to automatically use a specific credential for a given directory and its subdirectories. This per-directory scoping keeps each project's ngrok authtoken isolated, preventing accidental token resets or mix-ups when switching between projects on one machine. daily.dev surfaces practical setups like this for engineers juggling multiple project credentials."}},{"@type":"Question","name":"Can a team manage ngrok credentials centrally without giving everyone dashboard access?","acceptedAnswer":{"@type":"Answer","text":"Yes, with a 1Password Teams or Business account paired with the ngrok shell plugin, credentials can be issued and managed centrally by team, project, or individual, and team members never need to log into the ngrok dashboard directly to get their authtoken. Teams standardizing credential workflows can track integrations like this via daily.dev."}}]} ```