<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sohel Siddique</title>
    <description>The latest articles on DEV Community by Sohel Siddique (@teamonly).</description>
    <link>https://dev.to/teamonly</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4207528%2F5f99aa6c-5ad9-4d15-a8ac-f04259227982.png</url>
      <title>DEV Community: Sohel Siddique</title>
      <link>https://dev.to/teamonly</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/teamonly"/>
    <language>en</language>
    <item>
      <title>Internal tools, built with AI, for your team only</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Thu, 19 Nov 2026 07:10:26 +0000</pubDate>
      <link>https://dev.to/teamonly/internal-tools-built-with-ai-for-your-team-only-3gga</link>
      <guid>https://dev.to/teamonly/internal-tools-built-with-ai-for-your-team-only-3gga</guid>
      <description>&lt;p&gt;Last updated 25 October 2026. Written by TeamOnly. We make one of the options below, so prices link to each vendor's own page.&lt;/p&gt;

&lt;p&gt;The small apps a team runs on: a quote calculator, a stock count, an approval flow. You can now build one in an afternoon with an AI tool. This page is about getting it into your coworkers' hands without putting it on the open web.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Build the tool with Claude Code or Cursor, then put it on a host that checks your company login before the app loads. On TeamOnly that is one command, and coworkers sign in with the work account they already have.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is an internal tool?
&lt;/h2&gt;

&lt;p&gt;An app made for the people inside a company, not for customers. It does one job a team does every week, and only staff can open it.&lt;/p&gt;

&lt;p&gt;Most start as a spreadsheet, an email thread or someone's memory. They turn into a tool when enough people need the same answer. Here are ones teams actually build:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Quote calculator.&lt;/strong&gt; Sales prices a job in a minute, with today's rates and the right margin.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Inventory tracker.&lt;/strong&gt; Counts by location, a history of every change, and a list of what is running low. (Template)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Expense approval.&lt;/strong&gt; People send a receipt, a manager approves it, finance sees the month. (Template)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Request form.&lt;/strong&gt; One place to ask for a laptop, a repair or a day off, with a status people can check. (Template)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Customer lookup.&lt;/strong&gt; Find a customer by name or account number and read the team's notes. (Template)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask the docs.&lt;/strong&gt; Search the handbook and policies in plain words instead of asking the same person again. (Template)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Onboarding checklist.&lt;/strong&gt; What a new hire needs in week one, ticked off by each team that owns a step.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shift planner.&lt;/strong&gt; Who works when, who wants to swap, and who is short a person.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Equipment booking.&lt;/strong&gt; Meeting rooms, vans, cameras or test devices, without double bookings.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Site visit log.&lt;/strong&gt; Photos and notes from inspections or deliveries, sent from a phone.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  How do teams get internal tools today?
&lt;/h2&gt;

&lt;p&gt;There are four common routes, ours included. None is right for everyone. They differ in who builds, who can open the tool, and what you have to look after yourself.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;What it is like&lt;/th&gt;
&lt;th&gt;Suits&lt;/th&gt;
&lt;th&gt;Watch out for&lt;/th&gt;
&lt;th&gt;Cost&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A spreadsheet or form (Google Sheets, Excel, Forms)&lt;/td&gt;
&lt;td&gt;You already have it. Share the file and people start typing.&lt;/td&gt;
&lt;td&gt;A simple list a few people keep up to date&lt;/td&gt;
&lt;td&gt;Formulas get overwritten, everyone can see every row, and it gets slow and messy as more people use it.&lt;/td&gt;
&lt;td&gt;Included in Google Workspace or Microsoft 365&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;An internal tool builder (Retool, Appsmith, Softr and similar)&lt;/td&gt;
&lt;td&gt;You drag tables, forms and buttons onto a page in their editor and connect your data.&lt;/td&gt;
&lt;td&gt;Teams that want a visual editor and already keep their data in a database or another app&lt;/td&gt;
&lt;td&gt;People who use the tool need a user on that platform, often paid. You build inside their editor, not with your AI tool.&lt;/td&gt;
&lt;td&gt;Retool Team: $10 per builder and $5 per user a month, billed yearly. Appsmith Business: $15 per user a month. Both have a free plan for up to 5 users&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Build with AI, host it yourself (Claude Code, Cursor or Lovable, plus Vercel, Netlify or a server)&lt;/td&gt;
&lt;td&gt;Your AI tool writes the app. You pick a host, a database and a login, and connect them.&lt;/td&gt;
&lt;td&gt;Developers who already run apps and know how to lock one down&lt;/td&gt;
&lt;td&gt;Most hosts are public by default. Keeping it private, the secrets and the database are your job.&lt;/td&gt;
&lt;td&gt;Depends on the host and the services you add&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;Build with AI, host on TeamOnly&lt;/strong&gt; (company login built in)&lt;/td&gt;
&lt;td&gt;Your AI tool writes the app. One command puts it online behind your company login, with a database, file storage and secrets.&lt;/td&gt;
&lt;td&gt;Anyone who built a tool with Claude Code or Cursor and wants the team using it today&lt;/td&gt;
&lt;td&gt;Internal apps only, never public. The app is a React front end with a small JavaScript or TypeScript API. Python apps can't run here.&lt;/td&gt;
&lt;td&gt;Builder: $19 a month. Team: $249 a month. People who only use apps are free&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Checked 25 October 2026. Sources: &lt;a href="https://retool.com/pricing" rel="noopener noreferrer"&gt;Retool pricing&lt;/a&gt;, &lt;a href="https://www.appsmith.com/pricing" rel="noopener noreferrer"&gt;Appsmith pricing&lt;/a&gt;. For sharing an app you already built, see &lt;a href="https://teamonly.dev/guides/share-an-ai-built-app-with-your-team?ref=devto" rel="noopener noreferrer"&gt;the guide&lt;/a&gt; and &lt;a href="https://teamonly.dev/compare?ref=devto" rel="noopener noreferrer"&gt;the full comparison&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do I build one with AI and share it with my team?
&lt;/h2&gt;

&lt;p&gt;About ten minutes the first time. You need Node.js on your computer, which Claude Code and Cursor users already have.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Start free with your work email.&lt;/strong&gt; Try it free for 14 days, no card needed. After that, Builder is $19 a month for one builder and up to three apps. &lt;a href="https://teamonly.dev/pricing?ref=devto#trial" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#trial&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Start from a template, or from nothing.&lt;/strong&gt; Run &lt;code&gt;npx teamonly init --template inventory-tracker stock&lt;/code&gt; to get a ready-made app in a new folder called &lt;code&gt;stock&lt;/code&gt;, or &lt;code&gt;npx teamonly init&lt;/code&gt; in an empty folder for a blank one. Either way, your AI tool gets instructions for building apps that run on TeamOnly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask your AI tool for what you need.&lt;/strong&gt; Plain words are fine: "Add a reorder button that puts the item on a list for purchasing." Try it on your computer with &lt;code&gt;npm install&lt;/code&gt; and &lt;code&gt;npm run dev&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sign in once, then deploy.&lt;/strong&gt; Run &lt;code&gt;npx teamonly login&lt;/code&gt; the first time, then &lt;code&gt;npx teamonly deploy&lt;/code&gt;. You get a link like &lt;code&gt;stock.acme.teamonly.app&lt;/code&gt;. The database, file storage and secrets are created on the first deploy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Send the link.&lt;/strong&gt; Anyone at your company can open it. To narrow it to named people, run &lt;code&gt;npx teamonly access only dana@acme.com sam@acme.com&lt;/code&gt;.
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight console"&gt;&lt;code&gt;$ npx teamonly init --template inventory-tracker stock
✔ Created &lt;span class="s2"&gt;"stock"&lt;/span&gt; from the inventory-tracker template
$ &lt;span class="nb"&gt;cd&lt;/span&gt; stock &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; npm install
$ npx teamonly login
✔ Signed &lt;span class="k"&gt;in&lt;/span&gt; as dana@acme.com
$ npx teamonly deploy
✔ Live at https://stock.acme.teamonly.app
  Only @acme.com accounts can sign in.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Or just ask.&lt;/strong&gt; In Claude Code or Cursor, in the folder of your app, type "deploy this on TeamOnly". It runs the commands for you, asks for your work email and the code we send, and offers a 14-day free trial if your company has no plan yet.&lt;/p&gt;

&lt;h2&gt;
  
  
  Five templates to start from
&lt;/h2&gt;

&lt;p&gt;Each one already uses the company login and the database. Change it by asking your AI in plain words.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://teamonly.dev/templates/expense-approval?ref=devto" rel="noopener noreferrer"&gt;Expense approval&lt;/a&gt;: receipts, approvers and a monthly view for finance. &lt;code&gt;npx teamonly init --template expense-approval&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://teamonly.dev/templates/inventory-tracker?ref=devto" rel="noopener noreferrer"&gt;Inventory tracker&lt;/a&gt;: counts by location, reorder levels and low stock. &lt;code&gt;npx teamonly init --template inventory-tracker&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://teamonly.dev/templates/request-form?ref=devto" rel="noopener noreferrer"&gt;Request form&lt;/a&gt;: a queue marked new, in progress or done. &lt;code&gt;npx teamonly init --template request-form&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://teamonly.dev/templates/customer-lookup?ref=devto" rel="noopener noreferrer"&gt;Customer lookup&lt;/a&gt;: search customers and share notes. &lt;code&gt;npx teamonly init --template customer-lookup&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://teamonly.dev/templates/ask-the-docs?ref=devto" rel="noopener noreferrer"&gt;Ask the docs&lt;/a&gt;: search your handbook and policies. &lt;code&gt;npx teamonly init --template ask-the-docs&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What IT gets
&lt;/h2&gt;

&lt;p&gt;People are already building these tools. TeamOnly gives them one approved place to put them, and gives IT a clear view of all of it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Login before any app code runs.&lt;/strong&gt; Every request is checked for a signed-in person on your domain before it reaches the app. A builder can't switch it off.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every app in its own room.&lt;/strong&gt; Each app has its own database, file storage and secrets, and can't read another app's data.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One list of every app.&lt;/strong&gt; A dashboard shows each app, its owner, who can open it and how many emails it sent. Apps can only email people at your company. When someone leaves, an admin hands their apps to a new owner.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Never in search.&lt;/strong&gt; Every response tells search engines not to list the app, and nothing loads without a login anyway.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;On the Business plan, Okta or another SSO provider and audit logs are included, set up with your IT team. Signing someone out of every app at once works on every plan.&lt;/p&gt;

&lt;p&gt;More: &lt;a href="https://teamonly.dev/for-it?ref=devto" rel="noopener noreferrer"&gt;TeamOnly for IT&lt;/a&gt;, &lt;a href="https://teamonly.dev/security?ref=devto" rel="noopener noreferrer"&gt;security details&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  When TeamOnly is the wrong choice
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The app is for customers or the public. TeamOnly only hosts apps for people at your company.&lt;/li&gt;
&lt;li&gt;It is written in Python, or depends on Next.js server features. Those need a different host, or changes first.&lt;/li&gt;
&lt;li&gt;It has to reach a server that is only on your office network. Apps on TeamOnly can call services on the internet, not inside your network.&lt;/li&gt;
&lt;li&gt;You would rather build in a visual editor than with an AI tool. An internal tool builder suits that better.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Questions people ask
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is an internal tool?
&lt;/h3&gt;

&lt;p&gt;A small app used only by the people inside a company, like a quote calculator, an inventory tracker or an expense approval flow. It replaces a spreadsheet, a shared inbox or a manual step, and it should never be open to the public.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I build internal tools with AI if I don't code?
&lt;/h3&gt;

&lt;p&gt;Often, yes. Claude Code and Cursor write the code from a plain description, and the TeamOnly instructions keep it to a shape that deploys first time. Starting from a &lt;a href="https://teamonly.dev/templates?ref=devto" rel="noopener noreferrer"&gt;template&lt;/a&gt; makes it easier. You still need to be comfortable typing a few commands, or asking your AI tool to run them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where should I host an internal tool?
&lt;/h3&gt;

&lt;p&gt;Somewhere that checks your company login before the app loads, not a public host with a password. On TeamOnly, coworkers sign in with their work Google or Microsoft account, or a code sent to their work email, and nobody else gets in.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do my coworkers need an account or a paid seat?
&lt;/h3&gt;

&lt;p&gt;No. They sign in with the work account they already have. You pay for the people who build and deploy apps. Everyone who only uses them is free.&lt;/p&gt;

&lt;h3&gt;
  
  
  How is TeamOnly different from Retool or Appsmith?
&lt;/h3&gt;

&lt;p&gt;Retool and Appsmith are visual builders: you build in their editor, and each user of the tool is a user on their platform. TeamOnly is a host for apps your AI tool writes as ordinary code. The code is yours, and coworkers don't need a seat.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can an internal tool use our existing data?
&lt;/h3&gt;

&lt;p&gt;Each app has its own database. You can load data into it, for example from a CSV export, and the app can call other services that have an API, with the keys kept in secrets. On the Team plan an app can also read and update your company's own Postgres or MySQL database, even one inside your network. &lt;a href="https://teamonly.dev/databases?ref=devto" rel="noopener noreferrer"&gt;Company databases&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/how-it-works?ref=devto" rel="noopener noreferrer"&gt;How it works&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/templates?ref=devto" rel="noopener noreferrer"&gt;Templates&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/guides/share-an-ai-built-app-with-your-team?ref=devto" rel="noopener noreferrer"&gt;Share an AI-built app with your team&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/compare?ref=devto" rel="noopener noreferrer"&gt;Every option, side by side&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/pricing?ref=devto" rel="noopener noreferrer"&gt;Pricing&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Free for one app and up to 5 people, no time limit, no card: &lt;a href="https://teamonly.dev/pricing?ref=devto#free" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#free&lt;/a&gt;. Or try Builder free for 14 days: &lt;a href="https://teamonly.dev/pricing?ref=devto#trial" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#trial&lt;/a&gt;. Or subscribe: &lt;a href="https://teamonly.dev/pricing?ref=devto#subscribe" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#subscribe&lt;/a&gt; (Builder $19/mo, Team $249/mo)&lt;br&gt;
Not ready? Get updates: &lt;a href="https://teamonly.dev/waitlist?ref=devto" rel="noopener noreferrer"&gt;https://teamonly.dev/waitlist?ref=devto&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>tooling</category>
    </item>
    <item>
      <title>Retool alternatives for internal tools</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Tue, 10 Nov 2026 02:37:41 +0000</pubDate>
      <link>https://dev.to/teamonly/retool-alternatives-for-internal-tools-5g9n</link>
      <guid>https://dev.to/teamonly/retool-alternatives-for-internal-tools-5g9n</guid>
      <description>&lt;p&gt;Last updated 26 October 2026. Written by TeamOnly, one of the options below. Every other claim links to the vendor's own pages.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; If you want to self-host an open-source builder, look at Appsmith, ToolJet or Budibase. If you want an AI to build the app inside a platform, look at Superblocks, Zite or Vybe. If you already build with Claude Code or Cursor and want to keep the code, host it on TeamOnly: coworkers sign in with their work account and don't pay. One app for up to 5 people is free, and Builder is $19 a month. Retool itself now deploys React apps from Claude Code too, on paid plans with a seat for every user.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do the Retool alternatives compare?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;How you build&lt;/th&gt;
&lt;th&gt;Open source or self-host&lt;/th&gt;
&lt;th&gt;Who you pay for&lt;/th&gt;
&lt;th&gt;Paid plans start at&lt;/th&gt;
&lt;th&gt;Database included&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Retool&lt;/td&gt;
&lt;td&gt;Drag and drop, an AI assistant, or React code deployed with the Retool CLI (beta)&lt;/td&gt;
&lt;td&gt;Not open source. Self-host on Enterprise&lt;/td&gt;
&lt;td&gt;Every builder and every internal user&lt;/td&gt;
&lt;td&gt;Team: $10 per builder and $5 per user a month, billed yearly. Free to 5 users&lt;/td&gt;
&lt;td&gt;Yes, Retool Database&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Appsmith&lt;/td&gt;
&lt;td&gt;Drag and drop&lt;/td&gt;
&lt;td&gt;Yes, Apache-2.0. Self-host free&lt;/td&gt;
&lt;td&gt;Every user in a workspace. Builders cost nothing extra&lt;/td&gt;
&lt;td&gt;Business: $15 per user a month. Free to 5 users&lt;/td&gt;
&lt;td&gt;No, connect your own&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ToolJet&lt;/td&gt;
&lt;td&gt;Drag and drop, plus ToolJet AI from a description&lt;/td&gt;
&lt;td&gt;Yes, AGPL-3.0. Self-host free&lt;/td&gt;
&lt;td&gt;Builders, with a cap on end users per plan&lt;/td&gt;
&lt;td&gt;Basic: $23 per builder a month, billed yearly. Free for 2 builders and 50 end users&lt;/td&gt;
&lt;td&gt;Yes, ToolJet DB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Budibase&lt;/td&gt;
&lt;td&gt;Drag and drop, with automations and AI agents&lt;/td&gt;
&lt;td&gt;Yes, GPL v3 core. Self-host free&lt;/td&gt;
&lt;td&gt;Creators, plus end users as an add-on&lt;/td&gt;
&lt;td&gt;Pro: $19 a month for 1 creator. End users $5 each a month&lt;/td&gt;
&lt;td&gt;Yes, Budibase DB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Superblocks&lt;/td&gt;
&lt;td&gt;Describe it to Superblocks' AI agent, Clark, or import from Claude, Lovable or Replit&lt;/td&gt;
&lt;td&gt;Not open source. Your own cloud on Enterprise&lt;/td&gt;
&lt;td&gt;Builders. End users unlimited&lt;/td&gt;
&lt;td&gt;Teams: $125 a month, or $100 billed yearly, for 1 hosted app&lt;/td&gt;
&lt;td&gt;Uses your own database&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Zite&lt;/td&gt;
&lt;td&gt;Describe it to Zite's AI, or build with your own AI tool&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Nobody: unlimited users on every plan&lt;/td&gt;
&lt;td&gt;Pro: $20 a month, billed yearly. Free plan&lt;/td&gt;
&lt;td&gt;Yes, Postgres&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vybe&lt;/td&gt;
&lt;td&gt;Ask Vybe's AI agents, in Slack or the browser, to build a Next.js app you can download&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Nobody: plans are by AI credits, viewers unlimited&lt;/td&gt;
&lt;td&gt;Starter: $20 a month. Free plan&lt;/td&gt;
&lt;td&gt;Yes, PostgreSQL per app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Claude Code or Cursor + TeamOnly&lt;/td&gt;
&lt;td&gt;Chat with Claude Code or Cursor on your computer; the code is yours&lt;/td&gt;
&lt;td&gt;No. The apps are plain React and Hono you can move&lt;/td&gt;
&lt;td&gt;Builders. App users free&lt;/td&gt;
&lt;td&gt;Builder: $19 a month (1 builder, 3 apps). Team: $249 a month. Free plan for 1 app and up to 5 people&lt;/td&gt;
&lt;td&gt;Yes, one per app, plus files and secrets. Can also connect your own Postgres or MySQL (Team)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Checked 26 October 2026, US prices, monthly unless noted. Retool: &lt;a href="https://retool.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;, &lt;a href="https://retool.com/blog/retool-cli" rel="noopener noreferrer"&gt;Retool CLI&lt;/a&gt;, &lt;a href="https://docs.retool.com/apps/management/guides/import-export" rel="noopener noreferrer"&gt;import and export&lt;/a&gt;. Appsmith: &lt;a href="https://www.appsmith.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;, &lt;a href="https://github.com/appsmithorg/appsmith" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;. ToolJet: &lt;a href="https://www.tooljet.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;, &lt;a href="https://github.com/ToolJet/ToolJet" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;. Budibase: &lt;a href="https://budibase.com/pricing/" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;, &lt;a href="https://github.com/Budibase/budibase" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;, &lt;a href="https://docs.budibase.com/reference/appexport" rel="noopener noreferrer"&gt;app export&lt;/a&gt;. Superblocks: &lt;a href="https://www.superblocks.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;, &lt;a href="https://docs.superblocks.com/building-with-clark/import-app/claude" rel="noopener noreferrer"&gt;importing apps&lt;/a&gt;. Zite: &lt;a href="https://zite.com/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;, &lt;a href="https://www.zite.com/help/platform/access/authentication" rel="noopener noreferrer"&gt;sign-in&lt;/a&gt;. Vybe: &lt;a href="https://www.vybe.build/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;, &lt;a href="https://docs.vybe.build/apps/overview" rel="noopener noreferrer"&gt;apps&lt;/a&gt;. Vybe changed its prices this month; plans change often, so check the vendor's page before you pay.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build inside a platform, or bring your own code?
&lt;/h2&gt;

&lt;p&gt;Most Retool alternatives are app builders: you make the tool in their editor, and the app lives there. A newer option is to build with an AI coding tool on your computer and only pay someone to host it behind your company login.&lt;/p&gt;

&lt;h3&gt;
  
  
  An app builder (Retool, Appsmith, ToolJet, Budibase, Superblocks, Zite, Vybe)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Ready-made tables, forms and connectors to your databases and APIs.&lt;/li&gt;
&lt;li&gt;Nothing to install. Someone who has never written code can start.&lt;/li&gt;
&lt;li&gt;On most of them the app is in the platform's format, so leaving means rebuilding it. Vybe is the exception: you can download its Next.js code.&lt;/li&gt;
&lt;li&gt;On Retool, Appsmith and Budibase, every person who opens the app counts as a user you pay for.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Your own code, hosted (Claude Code or Cursor + TeamOnly)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;The AI writes ordinary React and TypeScript, and the code stays in your project.&lt;/li&gt;
&lt;li&gt;Anything the AI can build, the app can do. No editor limits.&lt;/li&gt;
&lt;li&gt;You work on your computer, in plain English with the AI. Apps can use your own Postgres or MySQL too.&lt;/li&gt;
&lt;li&gt;Coworkers who only use the app are free, however many there are.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When is each one the right pick?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Retool
&lt;/h3&gt;

&lt;p&gt;The best-known builder for internal tools: drag and drop parts, connect your databases and APIs, and Retool hosts it with login. Its AI assistant can build an app from a prompt, and since September 2026 the Retool CLI (public beta, paid cloud plans) deploys React apps you wrote with tools like Claude Code. Team is $10 per builder and $5 per internal user a month billed yearly ($12 and $7 monthly). Custom SSO, Git and self-hosting are on Enterprise. Apps export as Retool files, not as code you can run elsewhere.&lt;/p&gt;

&lt;p&gt;Right pick when: your apps sit on top of company databases and APIs, and paying per user is fine.&lt;/p&gt;

&lt;h3&gt;
  
  
  Appsmith
&lt;/h3&gt;

&lt;p&gt;An open-source builder, Apache-2.0, that you can self-host for free with Docker or Kubernetes. The cloud is free for up to 5 users, then Business is $15 per user a month with no extra charge for builders, up to 99 users. Google sign-in is on Free and Business; SAML and SCIM are on Enterprise ($2,500 a month for 100 users). It connects to your databases rather than including one.&lt;/p&gt;

&lt;p&gt;Right pick when: you want a Retool-style builder you can run on your own servers.&lt;/p&gt;

&lt;h3&gt;
  
  
  ToolJet
&lt;/h3&gt;

&lt;p&gt;Open source under AGPL-3.0, with a visual editor and ToolJet AI that drafts an app from a description. The free cloud plan covers 2 builders, 50 end users and 10 apps, with a small built-in database. Paid plans are per builder: Basic is $23 and Pro $79 a month billed yearly, and Team is $199 per builder billed yearly or $249 monthly. SSO through OIDC, LDAP or SAML starts on Team.&lt;/p&gt;

&lt;p&gt;Right pick when: a small team wants a free open-source builder with a database included.&lt;/p&gt;

&lt;h3&gt;
  
  
  Budibase
&lt;/h3&gt;

&lt;p&gt;An open-source builder for apps, automations and AI agents. Self-hosting the open-source version is free with unlimited users. On the cloud there is no free plan: Pro is $19 a month for 1 creator, and end users are a $5 a month add-on each. Exporting apps through the API needs an Enterprise license.&lt;/p&gt;

&lt;p&gt;Right pick when: you want forms and workflows with automations, and you can self-host.&lt;/p&gt;

&lt;h3&gt;
  
  
  Superblocks
&lt;/h3&gt;

&lt;p&gt;An AI-first builder: you describe the app to its agent, Clark, and it builds on Superblocks' integrations. You can import an app made in Claude, Lovable or Replit and Clark rewrites it. Teams is $125 a month, or $100 billed yearly, for up to 15 builders and 1 hosted app, with more apps at $10 each a month and unlimited end users. SSO is on Enterprise.&lt;/p&gt;

&lt;p&gt;Right pick when: iT wants a governed AI builder for the company and has a budget for it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Zite
&lt;/h3&gt;

&lt;p&gt;Describe the app to Zite's AI, or build it with your own AI tool. Every plan, even Free, has unlimited users. Pro is $20 a month and Business $75 a month, both billed yearly. Apps can use magic links, Google or a list of allowed email domains for sign-in; SSO is on Enterprise. A Postgres database is included.&lt;/p&gt;

&lt;p&gt;Right pick when: you want an AI builder with no per-user cost and a database built in.&lt;/p&gt;

&lt;h3&gt;
  
  
  Vybe
&lt;/h3&gt;

&lt;p&gt;Vybe is mainly AI agents that work with your team in Slack channels, and those agents can also build internal apps. Each app is a Next.js project you can read, download or clone with git, with its own PostgreSQL database. Apps are private to signed-in people in your organization and guests you share them with. Plans are by AI credits with unlimited builders and viewers: Free, then Starter $20, Pro $50 and Team $100 a month. SAML SSO is on Enterprise. Vybe changed its pricing in October 2026.&lt;/p&gt;

&lt;p&gt;Right pick when: your team lives in Slack and wants AI agents first, with internal apps as part of the package.&lt;/p&gt;

&lt;h3&gt;
  
  
  Claude Code or Cursor, hosted on TeamOnly
&lt;/h3&gt;

&lt;p&gt;TeamOnly isn't a builder. You build with Claude Code or Cursor on your computer, and &lt;code&gt;npx teamonly deploy&lt;/code&gt; puts the app online behind your company login. Coworkers sign in with their work Google or Microsoft account, or a code sent to their work email, and nobody else gets in. Each app gets its own database, file storage and secrets. Apps are React with a small TypeScript API, in your own repo. Apps can also read your company's own Postgres or MySQL database, even one inside your network, on the Team plan. Every deploy is a version you can roll back to. It is for internal apps only.&lt;/p&gt;

&lt;p&gt;Right pick when: you already build with an AI coding tool, want to keep the code, and don't want to pay for every coworker who opens the app.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is the best Retool alternative?
&lt;/h3&gt;

&lt;p&gt;It depends on how you want to build. For an open-source builder you can self-host, Appsmith, ToolJet or Budibase. For an AI that builds inside a platform, Superblocks, Zite or Vybe. If you already use Claude Code or Cursor and want to keep the code, host the app on TeamOnly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is there a free Retool alternative?
&lt;/h3&gt;

&lt;p&gt;Yes. Appsmith, ToolJet and Budibase are open source and free to self-host. On the cloud, Appsmith is free to 5 users, ToolJet to 2 builders and 50 end users, and Zite and Vybe have free plans. Retool itself is free for up to 5 users. TeamOnly is free for 1 app that up to 5 people can open, with no time limit, and Builder is $19 a month.&lt;/p&gt;

&lt;h3&gt;
  
  
  How much does Retool cost?
&lt;/h3&gt;

&lt;p&gt;Free for up to 5 users. Team is $10 per builder and $5 per internal user a month billed yearly, or $12 and $7 billed monthly. Business is $50 per builder and $15 per internal user a month billed yearly. Enterprise pricing isn't published.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I use Claude Code instead of Retool?
&lt;/h3&gt;

&lt;p&gt;For building, yes: Claude Code can write the whole app. What it doesn't do is share it. The app still needs hosting, a login limited to your company and a database. Retool's CLI is one way to get that, with a paid seat per user. TeamOnly is another, where coworkers sign in with their work account and don't pay.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I export a Retool app as code?
&lt;/h3&gt;

&lt;p&gt;Retool exports apps as JSON or a Toolscript ZIP that imports back into Retool. It isn't a React or HTML app you can run somewhere else, and resources and data aren't included. Moving off Retool usually means rebuilding the app.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do my coworkers need an account to use the app?
&lt;/h3&gt;

&lt;p&gt;On Retool, Appsmith and Budibase, each person is a user in that platform, and on paid plans you pay for them. On TeamOnly, coworkers sign in with their work Google or Microsoft account or an emailed code, and people who only use apps are free.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is TeamOnly open source or self-hosted?
&lt;/h3&gt;

&lt;p&gt;No. TeamOnly runs on Cloudflare in our account. The apps are standard React and Hono code with a SQLite database, and the code stays in your repo, so moving one to your own Cloudflare account is mostly configuration.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep your code. Skip the seats.
&lt;/h2&gt;

&lt;p&gt;Builder is $19 a month for 3 apps, free for 14 days. Coworkers sign in with their work account and don't pay.&lt;/p&gt;

&lt;p&gt;Start free: &lt;a href="https://teamonly.dev/pricing?ref=devto" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>lowcode</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Shadow AI apps: what IT can do about tools staff build with AI</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Sun, 08 Nov 2026 05:46:03 +0000</pubDate>
      <link>https://dev.to/teamonly/shadow-ai-apps-what-it-can-do-about-tools-staff-build-with-ai-50b1</link>
      <guid>https://dev.to/teamonly/shadow-ai-apps-what-it-can-do-about-tools-staff-build-with-ai-50b1</guid>
      <description>&lt;p&gt;Last updated 25 October 2026. Written by TeamOnly. We make one of the places builders can deploy to, and we say so where it comes up.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Assume these apps already exist. Find them without blame, then give builders one approved place to deploy: behind your company login, with a named owner for every app. A one-page policy covers the rest.&lt;/p&gt;

&lt;p&gt;Banning AI tools rarely works. It moves the apps somewhere you can't see. This page covers what shadow AI is, the real risks of AI-built internal apps, how to find what already exists, and a policy you can copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is shadow AI?
&lt;/h2&gt;

&lt;p&gt;Three terms that get mixed up. They describe the same habit at different stages.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Shadow IT:&lt;/strong&gt; software and services people use for work without IT knowing or approving. A personal file-sharing account, a project tool paid on someone's card.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shadow AI:&lt;/strong&gt; the same, with AI tools. Staff paste company data into chat assistants or AI features that IT has not reviewed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shadow AI apps:&lt;/strong&gt; the newer part. Staff use Claude Code, Cursor, Lovable, Replit, Bolt or v0 to build a working app, publish it, and send the link to coworkers. The app holds company data and keeps running.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The third one is different because it lasts. A chat is over in a minute. An app has users, data and a link that keeps working, often on the builder's own account.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vendor research:&lt;/strong&gt; In a Retool survey of 307 CTOs, CIOs and CISOs in May 2026, 8% said they had strong governance of AI-built internal tools, and 5% were very confident they could see everything running. Security company Red Access reported finding more than 380,000 publicly reachable assets on the main vibe-coding platforms. About 5,000 looked like company tools, and more than 2,000 of those held sensitive business, operational or personal data.&lt;/p&gt;

&lt;p&gt;Checked 25 October 2026. Sources: &lt;a href="https://retool.com/blog/ai-governance-report-2026" rel="noopener noreferrer"&gt;Retool AI Governance Report 2026&lt;/a&gt; (a vendor survey, June 2026), &lt;a href="https://thehackernews.com/2026/05/what-2000-exposed-vibe-coded-apps.html" rel="noopener noreferrer"&gt;summary of Red Access's research on The Hacker News&lt;/a&gt; (a contributed article, May 2026).&lt;/p&gt;

&lt;h2&gt;
  
  
  What can go wrong with AI-built internal apps?
&lt;/h2&gt;

&lt;p&gt;The code is rarely the main problem. Where the app lives, and who can open it, usually is.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Public links with company data.&lt;/strong&gt; Many app builders publish to the open web unless you pay for, or find, the private option. A link nobody was told about still gets shared, and sometimes indexed by search engines.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shared passwords.&lt;/strong&gt; A password on the whole app ends up in chat threads and emails. The app can't tell who did what, and people who leave still know it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apps on personal accounts.&lt;/strong&gt; The app runs on whatever platform the builder signed up for, billed to their card, under their login. The company has no admin access to it and may not know it exists.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No owner when someone leaves.&lt;/strong&gt; When the builder leaves, the app either keeps running with nobody responsible for it, or stops when their card is cancelled. Either way, the team that relied on it finds out last.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No list of what exists.&lt;/strong&gt; You can't review, fix or retire an app you don't know about. Without a list, every one of these risks is invisible.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Secrets in code, databases left open.&lt;/strong&gt; AI tools sometimes write API keys into code that runs in the browser, where anyone who opens the app can read them. A hosted database with row-level security turned off can be read without going through the app at all.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How do I find the apps that already exist?
&lt;/h2&gt;

&lt;p&gt;No single tool finds them all. These steps, together, find most of them in an afternoon.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Ask, without blame.&lt;/strong&gt; Send one short message: "If you built a tool with AI that coworkers use, tell us. Nothing gets switched off, we want to help you keep it running safely." Builders are usually glad someone asked.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check expense reports and card statements.&lt;/strong&gt; Look for Lovable, Replit, Bolt, Vercel, Netlify, Supabase, Cursor and Claude subscriptions. A builder platform on an expense report usually means an app somewhere.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check what people signed in to with their work account.&lt;/strong&gt; Google Workspace and Microsoft Entra both list the third-party apps people connected with their work account, and sign-in logs show which ones they use. Builder platforms show up there when people sign up with "Sign in with Google" or Microsoft.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Look for app addresses.&lt;/strong&gt; Search DNS or web proxy logs, and your company chat, for addresses like &lt;code&gt;*.lovable.app&lt;/code&gt;, &lt;code&gt;*.replit.app&lt;/code&gt;, &lt;code&gt;*.vercel.app&lt;/code&gt;, &lt;code&gt;*.netlify.app&lt;/code&gt; and &lt;code&gt;*.pages.dev&lt;/code&gt;. Links in chat are often the fastest way to find the apps people actually use.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check browser and device inventories, if you have them.&lt;/strong&gt; If you manage browsers or laptops, the inventory shows AI extensions and apps like Cursor or Claude installed. That tells you who is building, not what they built, so follow up by asking.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write it down.&lt;/strong&gt; One row per app: name, owner, where it is hosted, what data it holds, who uses it. That sheet is your first inventory, and it tells you which apps to move first.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  A vibe coding policy you can adopt
&lt;/h2&gt;

&lt;p&gt;Short enough that people read it. Change the parts in [brackets] and send it.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Policy: tools built with AI

1. What this covers. Any app, script or tool built with AI help (Claude Code,
   Cursor, Lovable, Replit, Bolt, v0 or similar) that someone other than its
   builder uses.
2. Building is allowed. Anyone may build tools for their own work. You don't
   need permission to try an idea.
3. Where apps live. Apps that coworkers use are deployed to [our approved
   host]. Not on a personal account, and not on public hosting.
4. Login comes first. Every app asks for a company account before it shows
   any screen or data. No shared passwords and no public links.
5. Data. Internal work data is fine. Customer personal data, payment card
   data, health data and passwords to other systems need a check with IT
   first. Company data never goes into an app on a personal account.
6. Keys and passwords. API keys and passwords go in the host's secret
   settings. Never in the code, and never in chat.
7. Every app has an owner. The owner keeps it working and decides who can
   open it: the whole company or a named list of people.
8. When someone leaves. Before someone leaves or changes role, their apps are
   handed to a new owner. An app nobody takes over is turned off.
9. Report, without blame. If you find an app with company data that anyone
   can open, tell [IT contact]. Nobody gets in trouble for reporting.
10. Review. IT reviews the list of apps every [quarter]. Apps nobody has used
    in [90 days] may be deleted after asking the owner.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Why not just ban it?
&lt;/h3&gt;

&lt;p&gt;People build these tools because they solve real problems. A ban doesn't remove the problem, it moves the tool to a personal account. One approved place to deploy gets you the same tools, behind your login, in a list you can read.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give builders somewhere safe to deploy
&lt;/h2&gt;

&lt;p&gt;The policy works when the approved host does the hard parts, so builders can't get them wrong. This is what TeamOnly does.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Login before any app code runs.&lt;/strong&gt; Every request to every app is checked first. People who are not signed in never reach the app. There is no setting to make an app public.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Only company accounts.&lt;/strong&gt; Coworkers sign in with work Google, work Microsoft or a code sent to their work email. Only your domains get in, and personal accounts are refused.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every app listed.&lt;/strong&gt; The dashboard shows every app in your company, its owner, who can open it and every deploy. Access is the whole company or a named list.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A new owner when people leave.&lt;/strong&gt; Admins hand an app to a new owner in the dashboard. Turn off someone's work account and new sign-ins stop. Admins choose how long app sign-ins last, from 8 hours to 30 days.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sign out everywhere.&lt;/strong&gt; An admin can sign a builder out of every terminal and the dashboard at once.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apps kept apart.&lt;/strong&gt; Each app has its own database, file storage and secrets, and its session cookie is scoped to its own address. Keys are set with &lt;code&gt;npx teamonly secrets set&lt;/code&gt;, outside the code.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The Free plan costs nothing: one app for up to 5 people, no time limit, no card. Builder is $19 a month for one builder and 3 apps. Team is $249 a month for unlimited apps and builders. People who only use apps are free. &lt;a href="https://teamonly.dev/pricing?ref=devto" rel="noopener noreferrer"&gt;Pricing&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Business plan:&lt;/strong&gt; On Business ($899 a month), Okta, OneLogin or other SSO, audit logs, offboarding, data region and paying by invoice are included, and we set them up with your IT team when you join.&lt;/p&gt;

&lt;p&gt;What it doesn't do: TeamOnly hosts internal web apps with a React front end and a JavaScript or TypeScript API. It doesn't host public websites or Python apps, and we have no SOC 2 or ISO certification today. &lt;a href="https://teamonly.dev/security?ref=devto" rel="noopener noreferrer"&gt;Security details&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions people ask
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is shadow AI?
&lt;/h3&gt;

&lt;p&gt;Shadow AI is staff using AI tools for work without IT knowing or approving, often with company data in them. It started with chat assistants. It now includes working apps that staff build with AI and share with coworkers.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the difference between shadow IT and shadow AI?
&lt;/h3&gt;

&lt;p&gt;Shadow IT is any software or service people use for work outside IT's view, like a file-sharing account or a project tool paid on a personal card. Shadow AI is the same thing with AI tools. Shadow AI apps go one step further: the staff member is not just using a tool, they built one, and it holds company data.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should we ban vibe coding?
&lt;/h3&gt;

&lt;p&gt;A ban rarely removes the need. People build these tools because they solve real problems, so a ban moves them to personal accounts where you can't see them. Most companies do better with a short policy and one approved place to deploy.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do we find the AI-built apps people already made?
&lt;/h3&gt;

&lt;p&gt;Ask, without blame. Then check expense reports for Lovable, Replit, Vercel and similar subscriptions, the list of third-party apps people connected with their work account in Google Workspace or Microsoft Entra, and DNS or chat logs for addresses like &lt;code&gt;*.lovable.app&lt;/code&gt; or &lt;code&gt;*.vercel.app&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  What should a vibe coding policy include?
&lt;/h3&gt;

&lt;p&gt;What people may build, where apps must be deployed, that every app needs a company login, what data is allowed, where keys and passwords go, who owns each app, and what happens when the owner leaves. The policy on this page fits on one page and can be copied as is.&lt;/p&gt;

&lt;h3&gt;
  
  
  Are AI-built apps a security risk?
&lt;/h3&gt;

&lt;p&gt;For internal tools, the bigger risk is usually where the app lives, not the code: a public link, a shared password, a personal account, keys written into the code, or nobody responsible once the builder leaves. Each of those can be fixed by the place the app is deployed to.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/for-it?ref=devto" rel="noopener noreferrer"&gt;TeamOnly for IT&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/security?ref=devto" rel="noopener noreferrer"&gt;Security details&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/pricing?ref=devto" rel="noopener noreferrer"&gt;Pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/guides/share-an-ai-built-app-with-your-team?ref=devto" rel="noopener noreferrer"&gt;Share an AI-built app with your team&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/company-login?ref=devto" rel="noopener noreferrer"&gt;Company-only login&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Free for one app and up to 5 people, no time limit, no card: &lt;a href="https://teamonly.dev/pricing?ref=devto#free" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#free&lt;/a&gt;. Or try Builder free for 14 days: &lt;a href="https://teamonly.dev/pricing?ref=devto#trial" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#trial&lt;/a&gt;. Or subscribe: &lt;a href="https://teamonly.dev/pricing?ref=devto#subscribe" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#subscribe&lt;/a&gt; (Builder $19/mo, Team $249/mo, Business $899/mo)&lt;br&gt;
For IT: &lt;a href="https://teamonly.dev/for-it?ref=devto" rel="noopener noreferrer"&gt;https://teamonly.dev/for-it?ref=devto&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>devops</category>
      <category>productivity</category>
    </item>
    <item>
      <title>GitHub Actions pricing 2026: Linux $0.006, macOS $0.062 per minute</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Sat, 07 Nov 2026 03:41:17 +0000</pubDate>
      <link>https://dev.to/macrun/github-actions-pricing-2026-linux-0006-macos-0062-per-minute-2m5n</link>
      <guid>https://dev.to/macrun/github-actions-pricing-2026-linux-0006-macos-0062-per-minute-2m5n</guid>
      <description>&lt;p&gt;GitHub Actions is free for public repositories and metered by the minute for private ones, with a different rate for every runner type. This page puts all the rates in one place. It explains how included minutes really get used. And it shows why the macOS line is the one that ends up on the invoice.&lt;/p&gt;

&lt;h2&gt;
  
  
  The per-minute rates
&lt;/h2&gt;

&lt;p&gt;These are GitHub's published rates for hosted runners on private repositories. They are per minute of wall-clock time. Every job is rounded up to the next minute:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  Linux 2-core (x64)          $0.006
  Linux 2-core (arm64)        $0.005
  Windows 2-core              $0.010
  macOS 3-core / 4-core       $0.062
  macOS 12-core               $0.077
  macOS 5-core (M2 Pro)       $0.102
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two things stand out. A standard macOS minute costs about ten times a Linux minute, and the largest macOS runner costs about seventeen times. Everything else on the invoice is small next to that column.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Building iOS or macOS apps?&lt;/strong&gt; That macOS column is where a dedicated Mac pays off. A flat $139 a month M6 runner covers about 2,242 metered minutes, and every build after that costs nothing. It works with GitHub Actions through a two-line change to your workflow. See &lt;a href="https://macrun.dev/pricing?ref=devto" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;, or try it for a day with a &lt;a href="https://macrun.dev/rent-a-mac-for-a-day?ref=devto" rel="noopener noreferrer"&gt;day pass&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How included minutes really work
&lt;/h2&gt;

&lt;p&gt;Paid plans include a block of minutes each month, roughly 2,000 on Free, 3,000 on Team and 50,000 on Enterprise. The catch is that the allowance is counted in Linux-equivalent minutes. A macOS minute consumes ten included minutes and a Windows minute consumes two. A single ten-minute iOS build therefore uses a hundred minutes of a 3,000-minute allowance.&lt;/p&gt;

&lt;p&gt;In practice, an iOS team on the Team plan uses up its allowance in the first week or two. It pays the metered rate for the rest of the month. The included minutes are not a discount on macOS work so much as a short grace period.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a real month looks like
&lt;/h2&gt;

&lt;p&gt;Take a small team that runs a 12-minute test suite on every pull request, about 20 pushes a working day. That is roughly 5,000 macOS minutes a month:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;  5,000 min  x  $0.062  =  $310/mo   (standard runner)
  5,000 min  x  $0.102  =  $510/mo   (largest runner)
  flat dedicated M6              $139/mo   (unlimited)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The flat machine wins from about 2,242 minutes a month upward at the standard rate, and the gap widens with every build after that. Put your own numbers into the &lt;a href="https://macrun.dev/calculator?ref=devto" rel="noopener noreferrer"&gt;calculator&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Costs that are not minutes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Storage.&lt;/strong&gt; Artifacts and caches beyond the included allowance bill per gigabyte per month. Large Xcode archives add up if retention is left at the default.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Re-downloads.&lt;/strong&gt; Hosted runners start clean, so every job re-fetches dependencies and rebuilds caches. That time is billed at the macOS rate too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Queue time is free, but not cheap.&lt;/strong&gt; Waiting for a macOS runner does not bill minutes, but it delays every merge.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The one decision that matters
&lt;/h2&gt;

&lt;p&gt;For teams that build daily, the question is not which macOS runner size to pick, it is whether to pay per minute at all. Below the break-even, metered billing is fine and simple. Above it, a dedicated Mac at a flat price is cheaper every month and gets faster as caches warm. The &lt;a href="https://macrun.dev/guides/github-actions-macos-minutes-cost?ref=devto" rel="noopener noreferrer"&gt;macOS minutes guide&lt;/a&gt; goes deeper on that math.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How much does GitHub Actions cost per minute?
&lt;/h3&gt;

&lt;p&gt;For private repositories: Linux 2-core $0.006, Windows 2-core $0.010, macOS 3- or 4-core $0.062, macOS 12-core $0.077. The 5-core M2 Pro macOS runner is $0.102 per minute. Public repositories are free on standard runners.&lt;/p&gt;

&lt;h3&gt;
  
  
  How are included minutes counted for macOS?
&lt;/h3&gt;

&lt;p&gt;Included minutes are measured in Linux-equivalent minutes. Each macOS minute uses ten included minutes and each Windows minute uses two, so a 3,000-minute allowance covers only about 300 macOS minutes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is GitHub Actions free for public repositories?
&lt;/h3&gt;

&lt;p&gt;Yes, standard hosted runners are free for public repositories. Larger runners and private repositories are billed per minute.&lt;/p&gt;

&lt;h3&gt;
  
  
  When does a dedicated Mac become cheaper than GitHub-hosted macOS?
&lt;/h3&gt;

&lt;p&gt;At the standard $0.062 rate, a flat $139 per month dedicated runner breaks even near 2,242 macOS minutes a month. Most teams building daily pass that point within the first two weeks.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This guide first appeared on &lt;a href="https://macrun.dev/guides/github-actions-pricing-explained?ref=devto" rel="noopener noreferrer"&gt;macrun.dev&lt;/a&gt;. Full disclosure, I run MacRun, which rents dedicated Mac minis for builds and coding agents.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>githubactions</category>
      <category>devops</category>
      <category>ci</category>
      <category>ios</category>
    </item>
    <item>
      <title>M6 Mac mini vs GitHub's hosted macOS runner: an Xcode build benchmark</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Wed, 04 Nov 2026 23:15:07 +0000</pubDate>
      <link>https://dev.to/macrun/m6-mac-mini-vs-githubs-hosted-macos-runner-an-xcode-build-benchmark-5efa</link>
      <guid>https://dev.to/macrun/m6-mac-mini-vs-githubs-hosted-macos-runner-an-xcode-build-benchmark-5efa</guid>
      <description>&lt;p&gt;We wanted a real number for one question. How much faster is a dedicated M6 Mac mini than GitHub's standard hosted macOS runner, on a real iOS app? So we built the open-source Wikipedia iOS app on both, with the same Xcode and the same script, three times each.&lt;/p&gt;

&lt;p&gt;This post replaces our earlier M4 benchmark post. Every number here comes from runs made on September 24, 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Results
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Median of 3 runs, in seconds. Lower is better.

                      GitHub-hosted   MacRun M6   change
                      macos-26
package download            43            39       -8%
clean build                183            86      -53%
incremental build           21            10      -51%
no-op build                 20            10      -50%
220 unit tests              44            17      -61%
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The M6 was about twice as fast at compiling. The package download was close, because both machines pull the same packages from GitHub over fast connections. Every step succeeded on both machines in every run.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a normal CI job costs in time
&lt;/h2&gt;

&lt;p&gt;The table compares the machines step by step. A real CI job is different on each. A hosted runner starts every job empty. It has to download packages, build from clean, and then test. A dedicated Mac keeps its build folder, so after a small change it only rebuilds what changed.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Full CI job, median of three runs.
GitHub-hosted, fresh VM   269 s
M6, empty caches          142 s
M6, warm caches            27 s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Hosted: download, clean build, tests. M6 warm: incremental build, tests.&lt;/p&gt;

&lt;p&gt;That is the gap your team feels. A job that took four and a half minutes finishes in under thirty seconds. On a busy day of pushes, the saved minutes add up to hours.&lt;/p&gt;

&lt;p&gt;The same job costs money on a hosted runner. GitHub rounds each job up to the minute, so 269 seconds bills as 5 minutes. At $0.062 a minute that is about 31 cents a job. On a dedicated Mac it costs nothing extra. Our &lt;a href="https://macrun.dev/calculator?ref=devto" rel="noopener noreferrer"&gt;cost calculator&lt;/a&gt; turns your own job count into a monthly figure.&lt;/p&gt;

&lt;h2&gt;
  
  
  The two machines
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub-hosted macos-26&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Apple M2 Pro (Virtual), 5 cores&lt;/li&gt;
&lt;li&gt;14 GB memory&lt;/li&gt;
&lt;li&gt;macOS 26.6.2, fresh VM per job&lt;/li&gt;
&lt;li&gt;Xcode 26.6 (17F113)&lt;/li&gt;
&lt;li&gt;Standard runner, $0.062 a minute&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;MacRun M6 mini&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Apple M6, 12 cores, bare metal&lt;/li&gt;
&lt;li&gt;16 GB memory&lt;/li&gt;
&lt;li&gt;macOS 27.0, same machine every job&lt;/li&gt;
&lt;li&gt;Xcode 26.6 (17F113)&lt;/li&gt;
&lt;li&gt;Flat $139 a month&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The hardware details come from the machines themselves. Each run printed its chip, core count and memory before building. GitHub also sells larger macOS runners at higher per-minute prices. We tested the standard one because it is what most teams use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Method
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Project: wikimedia/wikipedia-ios at commit 8691a89, built for the iOS Simulator with its Wikipedia scheme and Swift packages.&lt;/li&gt;
&lt;li&gt;Simulator: a new iPhone 17 on iOS 26.5, created the same way on both machines.&lt;/li&gt;
&lt;li&gt;Every run starts with the package cache and DerivedData deleted. Signing is off, as it usually is for CI simulator builds.&lt;/li&gt;
&lt;li&gt;Package download: &lt;code&gt;xcodebuild -resolvePackageDependencies&lt;/code&gt; into an empty folder.&lt;/li&gt;
&lt;li&gt;Clean build: &lt;code&gt;xcodebuild build-for-testing&lt;/code&gt; with empty DerivedData and packages already downloaded.&lt;/li&gt;
&lt;li&gt;Incremental build: the same command after adding one comment line to one Swift file in the app.&lt;/li&gt;
&lt;li&gt;No-op build: the same command again with nothing changed.&lt;/li&gt;
&lt;li&gt;Tests: the 220 unit tests in the app's WMFData package, run with &lt;code&gt;test-without-building&lt;/code&gt; on a booted simulator.&lt;/li&gt;
&lt;li&gt;Three full runs on each machine. We report the median.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Caveats
&lt;/h2&gt;

&lt;p&gt;We ran the app's package tests, not its main test target. The main target needs signed app-group entitlements, and an unsigned CI build does not have them. Its test host kept relaunching on both machines, so it was no fair measure.&lt;/p&gt;

&lt;p&gt;The incremental build touched one small file. Most of its 10 seconds is Xcode planning the build, which is why it matches the no-op build. A change to a widely used file would take longer on both machines.&lt;/p&gt;

&lt;p&gt;The two machines ran different macOS versions, because each ran what its owner ships today. A hosted job can also cache Swift packages with &lt;code&gt;actions/cache&lt;/code&gt;. That would cut the download step. It would not remove the clean build, which is most of the time.&lt;/p&gt;

&lt;p&gt;We sell the M6 runner, so weigh our numbers with that in mind. The method above is complete enough to rerun on your own project, which is the only benchmark that really matters to you.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This guide first appeared on &lt;a href="https://macrun.dev/blog/m6-mac-mini-vs-github-hosted-macos-runner-benchmark?ref=devto" rel="noopener noreferrer"&gt;macrun.dev&lt;/a&gt;. Full disclosure, I run MacRun, which rents dedicated Mac minis for builds and coding agents.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ios</category>
      <category>githubactions</category>
      <category>devops</category>
      <category>macos</category>
    </item>
    <item>
      <title>How to secure a vibe-coded app before you share it</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Fri, 30 Oct 2026 08:40:49 +0000</pubDate>
      <link>https://dev.to/teamonly/how-to-secure-a-vibe-coded-app-before-you-share-it-3i90</link>
      <guid>https://dev.to/teamonly/how-to-secure-a-vibe-coded-app-before-you-share-it-3i90</guid>
      <description>&lt;p&gt;Last updated 26 October 2026. Written by TeamOnly. We host internal apps built with AI, and each item says honestly where we help and where we don't.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Before coworkers use an app you built with AI, check four things first: nobody gets past a company login, only your company's accounts get in, no keys are in the code that runs in the browser, and the database can't be read without going through the app. Then check who can do what inside it, and who owns it when you leave.&lt;/p&gt;

&lt;p&gt;Most leaks from AI-built apps are not clever attacks. They are open doors: a public link, a database with its rules turned off, a key in the page. This checklist is for the person who built the app and the IT person reviewing it. Each item says what goes wrong, how to check it in plain words, and what TeamOnly handles and what is still on you.&lt;/p&gt;

&lt;h2&gt;
  
  
  What goes wrong with AI-built apps
&lt;/h2&gt;

&lt;p&gt;AI tools are good at making an app work. They are less careful about who else it works for. Three findings from the last two years show the pattern.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;380,000&lt;/strong&gt; publicly reachable assets found on Lovable, Base44, Netlify and Replit by the security company Red Access in May 2026. About 5,000 held sensitive company data, and many were indexed by Google.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;170 of 1,645&lt;/strong&gt; Lovable apps checked in March 2025 let anyone read or change data in their Supabase database without signing in, because the database access rules were missing or wrong (CVE-2025-48757).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;205,474&lt;/strong&gt; made-up package names suggested by 16 AI models across 576,000 code samples, in a 2025 study. Attackers can publish packages under those names and wait for someone to install them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of these needed a clever attacker. The doors were open. That is good news: open doors are easy to check for, and you don't need to read code to do it.&lt;/p&gt;

&lt;p&gt;Checked 26 October 2026. Sources: &lt;a href="https://securityboulevard.com/2026/05/thousands-of-vibe-coded-apps-exposing-corporate-personal-data-redaccess/" rel="noopener noreferrer"&gt;Security Boulevard on Red Access's findings&lt;/a&gt; (May 2026), &lt;a href="https://mattpalmer.io/posts/statement-on-CVE-2025-48757/" rel="noopener noreferrer"&gt;Matt Palmer, statement on CVE-2025-48757&lt;/a&gt; (2025), &lt;a href="https://arxiv.org/abs/2406.10279" rel="noopener noreferrer"&gt;Spracklen et al., "We Have a Package for You!"&lt;/a&gt; (USENIX Security 2025).&lt;/p&gt;

&lt;h2&gt;
  
  
  11 checks before you share the link
&lt;/h2&gt;

&lt;p&gt;Do them in order. The first ones keep strangers out, the later ones catch mistakes inside the company.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Nothing loads before a company login
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; AI tools often build the sign-in screen as one page of the app. The rest of the app, and its API, still answer anyone who skips that page or calls the API directly. Red Access found company apps that gave admin access to anyone who reached the address.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Open the app in a private browser window. You should see a sign-in screen and nothing else. Then ask your AI tool: "List every API route and tell me which ones work without signing in." The answer should be none.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Handled. Every request to every app is checked before any of your code runs, including API calls, which get a 401 without a session. There is no setting to make an app public.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Only your company's accounts get in
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; "Sign in with Google" lets any Google account in by default, including personal Gmail. Google's &lt;code&gt;hd&lt;/code&gt; setting only narrows the account picker, and Google warns not to rely on it because the request can be changed. The domain has to be checked on the server.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Try to sign in with a personal Gmail or Outlook account. You should be turned away. Ask your AI tool where the server checks the email domain, and whether it checks the signed token from Google or a value the browser sent.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Handled. Coworkers sign in with work Google, work Microsoft or a code sent to their work email. The domain in the verified sign-in token is checked against your company's domains, and personal accounts are refused.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Only the right people inside the company
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; An app with salaries, reviews or customer data gets shared with the whole company because that was the default. Or the AI builds its own allowlist in code that nobody updates.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Ask: should everyone at the company see this data? If not, write down the names of the people who should, and check that someone outside that list is turned away.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Handled, you choose. Access is the whole company or a named list, set in the dashboard or with &lt;code&gt;npx teamonly access only priya@acme.com&lt;/code&gt;. It is checked on every request, so removing someone takes effect within a minute.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Not on a public link, not in search results
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; Some app builders publish to a public address unless you choose private. Public apps get found: Red Access reported that many of the exposed company apps were indexed by Google and other search engines.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Search Google for &lt;code&gt;site:&lt;/code&gt; followed by your app's address. Check the project's visibility setting on the platform you built it with. If it says public, change it before anything else.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Handled. Apps live at &lt;code&gt;yourapp.yourcompany.teamonly.app&lt;/code&gt; behind the sign-in screen. Every response, including the sign-in screen, tells search engines not to index it, and the sign-in screen shows only the app's name and the ways to sign in.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. No keys in the code that runs in the browser
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; AI tools put API keys in the React code or in variables starting with &lt;code&gt;VITE_&lt;/code&gt; or &lt;code&gt;NEXT_PUBLIC_&lt;/code&gt;. Everything sent to the browser can be read by anyone who opens the app. Supabase says its secret key must never be in a browser, because it skips every database rule.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Ask your AI tool: "Is any key, token or password in front-end code, a &lt;code&gt;VITE_&lt;/code&gt; variable or a committed &lt;code&gt;.env&lt;/code&gt; file?" In the browser, open the developer tools and search the loaded files for &lt;code&gt;key&lt;/code&gt;, &lt;code&gt;secret&lt;/code&gt; and &lt;code&gt;sk_&lt;/code&gt;. If a key was ever exposed, change it at the service that issued it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Partly handled. Keys are stored with &lt;code&gt;npx teamonly secrets set NAME&lt;/code&gt;, outside the code, and only your app's server code can read them. The instructions TeamOnly adds tell your AI tool never to use &lt;code&gt;VITE_&lt;/code&gt; keys. Nothing stops you from pasting a key into the code yourself, so still check.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. The database can't be read around the app
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; With Supabase and similar services, the browser talks to the database directly and access rules (row-level security) decide what it can see. When those rules are off or wrong, anyone with the public key can read or change whole tables. That was the Lovable finding.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; In Supabase, open Advisors, then Security Advisor. Any "RLS disabled in public" error means a table anyone can read. A rule existing is not enough: sign in as an ordinary coworker and try to open someone else's record.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Handled for outsiders. Each app's database has no address of its own on the internet. It is only reachable through your app's server code, after sign-in. Which rows each signed-in person may see is still your app's code to get right (see check 8).&lt;/p&gt;

&lt;h3&gt;
  
  
  7. Each app's data kept apart
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; Several apps share one database or one storage bucket because it was quicker. Then a key or a bug in one app opens all of them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Ask: does any other app use the same database, storage or keys as this one? If yes, the weakest app decides how safe all of them are.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Handled. Each app gets its own database, file storage and secrets on first deploy, and its session cookie is tied to its own address. Apps can't reach each other's data.&lt;/p&gt;

&lt;h3&gt;
  
  
  8. Who can do what, checked on the server
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; The AI hides the Approve button from most people but leaves the approve route open to anyone signed in. Or the server trusts a role or email the browser sends. Broken access control is number one in the OWASP Top 10. Unchecked input is a cousin: a negative amount, a SQL query built from a text box.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Sign in as an ordinary coworker and try what only managers should do. Ask your AI tool: "For each API route, who may call it, and where on the server is that checked? Do all database queries use placeholders?"&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Partly handled. Your app gets the verified person (&lt;code&gt;ctx.user&lt;/code&gt;) and the roles you give out in the dashboard (&lt;code&gt;ctx.user.roles&lt;/code&gt;), and faked identity headers are removed. The instructions tell your AI tool to use query placeholders and check input on the server. Checking the role in each route is your app's code. TeamOnly doesn't review it.&lt;/p&gt;

&lt;h3&gt;
  
  
  9. Every package is real and needed
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; AI tools sometimes suggest packages that don't exist. Attackers publish packages under those names, so installing one runs a stranger's code inside your app.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Open &lt;code&gt;package.json&lt;/code&gt;. For any name you don't recognise, look it up on npmjs.com: a real package has a history, a linked source repository and steady downloads. Run &lt;code&gt;npm audit&lt;/code&gt; before you deploy, and remove packages the app no longer uses.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Not handled. TeamOnly doesn't scan packages. An app can only reach its own data and keys, which limits what a bad package can touch, but inside that app it could still read everything.&lt;/p&gt;

&lt;h3&gt;
  
  
  10. A record of who changed what
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; Something gets approved, deleted or changed and nobody can say who did it. AI-built apps rarely keep a history unless you ask for one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Ask your AI tool to record who created and last changed each record, and when, and to keep a history table for approvals and deletions. Try it: change a record, then look for your name on it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Partly handled. The dashboard shows every deploy of every app, with who deployed and when, and live logs. Logs are live, not stored. Audit logs of sign-ins and access changes are on the Business plan, set up with you. History inside the app (who approved an expense) is your app's job.&lt;/p&gt;

&lt;h3&gt;
  
  
  11. An owner, a backup and a plan for leavers
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;What goes wrong:&lt;/strong&gt; The builder leaves and the app keeps running on their personal account, or stops when their card is cancelled. Or a bad change wipes a table and there is no copy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Check it yourself:&lt;/strong&gt; Write down who owns the app and who takes over. Keep the code in a company Git repository. Ask your AI tool to add a CSV export of the main tables, and try it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On TeamOnly:&lt;/strong&gt; Mostly handled. Apps belong to your company, and admins can hand an app to a new owner. When someone leaves, an admin signs them out of every app at once and can block them until their work account is turned off. Every deploy is a version you can put back in seconds, and &lt;code&gt;npx teamonly export&lt;/code&gt; (or Download database in the dashboard) gives you the database and files. There are no automatic backups you restore yourself, so export before a risky change.&lt;/p&gt;

&lt;h2&gt;
  
  
  The one-minute check
&lt;/h2&gt;

&lt;p&gt;Eleven yes-or-no questions. Any "no" is the next thing to fix.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Before I share this app

[ ] A private browser window shows a company sign-in and nothing else.
[ ] A personal Gmail or Outlook account is turned away.
[ ] Only the people who need this data can open it.
[ ] A site: search for the app's address finds nothing.
[ ] No key, token or password is in the browser code or the repository.
[ ] The database can't be reached without going through the app.
[ ] This app's data and keys are not shared with any other app.
[ ] An ordinary coworker can't do what only managers should.
[ ] Every package in package.json is real and still used.
[ ] Records show who created and changed them.
[ ] Someone else knows they own this app if I leave, and the data can be exported.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Reviewing an app someone built
&lt;/h2&gt;

&lt;p&gt;Fifteen minutes with the builder, screen shared. You are checking setup, not reading every line of code.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Where it lives and who can reach it.&lt;/strong&gt; Get the address. Open it from a device that is not signed in, and from a personal account. Ask which platform hosts it and whose account pays for it. A personal account is the first thing to change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What data it holds.&lt;/strong&gt; Ask what goes in and where it comes from. Customer personal data, payment data, health data or passwords to other systems raise the bar, and may mean the app should be limited to a named list.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Where the keys are.&lt;/strong&gt; List every outside service the app calls. Each key should be in the host's secret settings, scoped to what the app needs, and not shared with other apps. Rotate any key that was ever in the code or in chat.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Who can do what.&lt;/strong&gt; Have the builder sign in as an ordinary user, or ask a coworker to, and try the admin actions. Ask the builder to have their AI tool list each API route and where it checks the role. Gaps here are fixed in the app's code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Packages and code.&lt;/strong&gt; Look at &lt;code&gt;package.json&lt;/code&gt; together and run &lt;code&gt;npm audit&lt;/code&gt;. Ask that the code lives in a company Git repository, not only on the builder's laptop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Owner, and the day they leave.&lt;/strong&gt; Write the app, its owner, a backup owner, its data and its users in your app list. Agree what happens when the owner leaves. The &lt;a href="https://teamonly.dev/guides/shadow-ai-apps?ref=devto" rel="noopener noreferrer"&gt;shadow AI apps guide&lt;/a&gt; has a one-page policy you can copy.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Shorter on TeamOnly:&lt;/strong&gt; On TeamOnly, the platform answers the first question for every app: login before any code runs, company domains only, out of search engines, and data and keys kept per app. The dashboard lists every app, its owner, who can open it and every deploy. Your review can spend its time on data, roles, packages and the owner.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions people ask
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Are vibe-coded apps safe to share with coworkers?
&lt;/h3&gt;

&lt;p&gt;They can be. The common problems are where the app lives and how it was set up: a public link, no real login, keys in the browser, database rules turned off. Each one can be checked in a few minutes. Run the checklist on this page before you send the link.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the biggest security risk in a vibe-coded app?
&lt;/h3&gt;

&lt;p&gt;Data anyone can reach without signing in. That usually happens in one of two ways: the app is on a public link with no login in front of it, or the database answers requests directly and its access rules are off (row-level security in Supabase). Both are about setup, not about the AI writing bad code.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is it safe to put my Supabase anon key in the browser?
&lt;/h3&gt;

&lt;p&gt;The anon or publishable key is made to be in the browser, but only because row-level security limits what it can reach. If row-level security is off on a table, anyone with that key can read and change it. The secret or &lt;code&gt;service_role&lt;/code&gt; key must never be in the browser: it skips every rule.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does "Sign in with Google" limit an app to my company?
&lt;/h3&gt;

&lt;p&gt;Not on its own. By default any Google account can sign in, including personal Gmail. Google's &lt;code&gt;hd&lt;/code&gt; setting only narrows the account picker, and Google says not to rely on it. The app's server has to check the domain in the verified sign-in token on every request.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I check if my app is indexed by Google?
&lt;/h3&gt;

&lt;p&gt;Search Google for &lt;code&gt;site:&lt;/code&gt; followed by your app's address, for example &lt;code&gt;site:myapp.lovable.app&lt;/code&gt;. If pages show up, the app is public and indexed. Make the app private or move it behind a company login, then ask Google to remove the pages with the Removals tool in Search Console if you own the domain.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I tell my AI tool to write secure code?
&lt;/h3&gt;

&lt;p&gt;Yes, and it is better to give it standing instructions than to ask once. A rules file in the project (&lt;code&gt;CLAUDE.md&lt;/code&gt;, &lt;code&gt;AGENTS.md&lt;/code&gt; or a Cursor rule) tells the tool where keys go, how to write database queries and where to check roles. &lt;code&gt;npx teamonly init&lt;/code&gt; adds these for TeamOnly apps. Then still run the checks yourself: instructions reduce mistakes, they don't remove them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does TeamOnly scan my app's code for security problems?
&lt;/h3&gt;

&lt;p&gt;No. TeamOnly puts a company login in front of every app, keeps each app's data and keys apart, and keeps apps out of search engines. It does not review your code, scan your packages or check the rules inside your app. Those items on the checklist are still yours.&lt;/p&gt;

&lt;h3&gt;
  
  
  What should IT check before approving an AI-built app?
&lt;/h3&gt;

&lt;p&gt;Where it is hosted and who can reach it, how sign-in is restricted, where the keys are, what data it holds, who owns it, and what happens when that person leaves. The "For IT" section on this page is a short review you can run in 15 minutes with the builder.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://teamonly.dev/security?ref=devto" rel="noopener noreferrer"&gt;Security details&lt;/a&gt;: Sign-in, isolation, cookies and secrets, in detail.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://teamonly.dev/for-it?ref=devto" rel="noopener noreferrer"&gt;TeamOnly for IT&lt;/a&gt;: Login first, isolation, inventory and offboarding, for the security review.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://teamonly.dev/guides/shadow-ai-apps?ref=devto" rel="noopener noreferrer"&gt;Shadow AI apps&lt;/a&gt;: How IT finds the apps people already built, and a policy to copy.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://teamonly.dev/company-login?ref=devto" rel="noopener noreferrer"&gt;Company-only login&lt;/a&gt;: Work Google, work Microsoft or an emailed code. Who gets in, who is turned away.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Checked 26 October 2026. Other sources: &lt;a href="https://developers.google.com/identity/openid-connect/openid-connect" rel="noopener noreferrer"&gt;Google, OpenID Connect&lt;/a&gt; (the &lt;code&gt;hd&lt;/code&gt; parameter), &lt;a href="https://supabase.com/docs/guides/api/api-keys" rel="noopener noreferrer"&gt;Supabase, API keys&lt;/a&gt;, &lt;a href="https://supabase.com/docs/guides/database/postgres/row-level-security" rel="noopener noreferrer"&gt;Supabase, Row Level Security&lt;/a&gt;, &lt;a href="https://supabase.com/docs/guides/database/database-advisors" rel="noopener noreferrer"&gt;Supabase, Database Advisors&lt;/a&gt;, &lt;a href="https://top10.owasp.org/2025" rel="noopener noreferrer"&gt;OWASP Top 10:2025&lt;/a&gt;, &lt;a href="https://retool.com/resources/how-to-secure-vibe-coded-apps" rel="noopener noreferrer"&gt;Retool, Secure vibe coding&lt;/a&gt; (a longer checklist for teams that run their own hosting).&lt;/p&gt;

&lt;p&gt;Try it free for 14 days, no card: &lt;a href="https://teamonly.dev/pricing?ref=devto#trial" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#trial&lt;/a&gt;. Or subscribe: &lt;a href="https://teamonly.dev/pricing?ref=devto#subscribe" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#subscribe&lt;/a&gt; (Builder $19/mo, Team $249/mo, Business $899/mo)&lt;br&gt;
For IT: &lt;a href="https://teamonly.dev/for-it?ref=devto" rel="noopener noreferrer"&gt;https://teamonly.dev/for-it?ref=devto&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>webdev</category>
      <category>devops</category>
    </item>
    <item>
      <title>Claude Code stops when your Mac sleeps: 5 fixes, lid closed too</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Mon, 26 Oct 2026 12:32:08 +0000</pubDate>
      <link>https://dev.to/macrun/claude-code-stops-when-your-mac-sleeps-5-fixes-lid-closed-too-1o7o</link>
      <guid>https://dev.to/macrun/claude-code-stops-when-your-mac-sleeps-5-fixes-lid-closed-too-1o7o</guid>
      <description>&lt;p&gt;You gave Claude Code a long task, closed the lid, and came back to a dead session. Nothing is wrong with the agent. macOS put the machine to sleep, and sleep suspends every process, drops the network, and ends any SSH connection. This page covers the settings that stop that, in the order to try them, and the point where the honest fix is a different machine.&lt;/p&gt;

&lt;h2&gt;
  
  
  What actually happens at sleep
&lt;/h2&gt;

&lt;p&gt;When a Mac sleeps, the CPU stops running your processes. The agent is not killed. It is frozen. When the machine wakes, the process continues. By then the API connection it was using has timed out. The tool call it was in the middle of has failed. On a laptop, a closed lid means sleep within seconds unless something prevents it. A lock screen does not cause sleep. A screensaver does not either. Only the sleep timer and the lid do.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 1: caffeinate for a single task
&lt;/h2&gt;

&lt;p&gt;macOS ships a tool that holds the machine awake while a command runs. Start the agent through it and the Mac stays up until the agent exits.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;caffeinate &lt;span class="nt"&gt;-i&lt;/span&gt; claude
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The flag keeps the system from idle sleeping. Add a second flag to keep the display on too, which matters only for tools that drive the screen.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;caffeinate &lt;span class="nt"&gt;-di&lt;/span&gt; claude
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This does not survive a closed laptop lid. The lid switch overrides every idle assertion. It also does nothing after the agent exits and you start the next task without it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 2: turn off sleep for the machine
&lt;/h2&gt;

&lt;p&gt;On a desktop Mac, or a laptop on power, set the sleep timer to never and leave it. These are the settings we use on every agent Mac.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; &lt;span class="nb"&gt;sleep &lt;/span&gt;0
&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; disksleep 0
&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; displaysleep 10
&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; womp 1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The display can still sleep. That saves power and changes nothing for a terminal process. The last line enables wake on network, which helps if something does put the machine down.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 3: the closed lid
&lt;/h2&gt;

&lt;p&gt;A MacBook with the lid closed sleeps unless it is on power and connected to an external display, keyboard, or mouse. That is Apple's clamshell rule. Without a display, one more setting forces the machine to stay awake with the lid shut.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;pmset &lt;span class="nt"&gt;-a&lt;/span&gt; disablesleep 1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Undo it later with the same command and a zero. Two warnings. The laptop will run warm in a bag or on a bed, so leave it on a hard surface. And it will drain a battery in a few hours if the power cable comes out, then die without a clean shutdown.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 4: the terminal, not the machine
&lt;/h2&gt;

&lt;p&gt;Sometimes the Mac stayed awake and the session still vanished. That is the terminal window closing or the SSH connection dropping, which sends a hangup to everything inside it. The answer is a terminal multiplexer. Run the agent inside a tmux session and it survives the window, the SSH drop, and the Wi-Fi hiccup.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;brew &lt;span class="nb"&gt;install &lt;/span&gt;tmux
tmux new &lt;span class="nt"&gt;-s&lt;/span&gt; agent
claude
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Detach with Ctrl-b then d. Reattach later from any terminal, or from your phone over SSH, with one command.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;tmux attach &lt;span class="nt"&gt;-t&lt;/span&gt; agent
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;There is a full guide to this setup: &lt;a href="https://macrun.dev/guides/keep-claude-code-session-alive-with-tmux?ref=devto" rel="noopener noreferrer"&gt;keeping a Claude Code session alive with tmux&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix 5: come back after a reboot
&lt;/h2&gt;

&lt;p&gt;Security updates restart the machine. Power blips restart it. After a restart nothing is running until someone logs in. For a machine that is meant to be unattended, enable automatic login for the agent user in System Settings. Then add a LaunchAgent that recreates the tmux session at login. The &lt;a href="https://macrun.dev/guides/always-on-mac-for-ai-agents?ref=devto" rel="noopener noreferrer"&gt;always-on Mac checklist&lt;/a&gt; has the full list, including battery backup.&lt;/p&gt;

&lt;h2&gt;
  
  
  When the laptop is the wrong machine
&lt;/h2&gt;

&lt;p&gt;Everything above works. It also turns your laptop into a server you cannot take anywhere. Once the agent is doing real work overnight, most people move it to a machine whose only job is to stay on. There are four choices. A spare Mac mini at home. A Linux box, if you do not need Xcode. A Mac in a cloud. Or a hosted Mac mini that someone else keeps awake. The &lt;a href="https://macrun.dev/guides/where-to-run-a-24-7-coding-agent?ref=devto" rel="noopener noreferrer"&gt;comparison of places to run a 24/7 agent&lt;/a&gt; has the costs side by side.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does caffeinate keep Claude Code running with the lid closed?
&lt;/h3&gt;

&lt;p&gt;No. The lid switch overrides caffeinate on a MacBook. You need the machine on power with an external display connected, or the disablesleep power setting.&lt;/p&gt;

&lt;h3&gt;
  
  
  Will the lock screen or screensaver stop the agent?
&lt;/h3&gt;

&lt;p&gt;No. Locking the screen and running the screensaver do not sleep the machine. Only the sleep timer, low battery, or a closed lid do. A locked screen is fine for a terminal agent.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does this apply to Codex too?
&lt;/h3&gt;

&lt;p&gt;Yes. Codex CLI is a terminal process like Claude Code. The same sleep settings, caffeinate, and tmux apply, and the same lid rule.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I keep the Mac awake from my phone?
&lt;/h3&gt;

&lt;p&gt;You can start a task from your phone with Claude Code's Remote Control or over SSH, but you cannot stop a Mac from sleeping remotely once it decides to. Set the power settings once on the machine itself.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This guide first appeared on &lt;a href="https://macrun.dev/guides/claude-code-stops-when-mac-sleeps?ref=devto" rel="noopener noreferrer"&gt;macrun.dev&lt;/a&gt;. Full disclosure, I run MacRun, which rents dedicated Mac minis for builds and coding agents.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>claudecode</category>
      <category>ai</category>
      <category>macos</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to share an app you built with AI, just with your team</title>
      <dc:creator>Sohel Siddique</dc:creator>
      <pubDate>Mon, 26 Oct 2026 01:52:30 +0000</pubDate>
      <link>https://dev.to/teamonly/how-to-share-an-app-you-built-with-ai-just-with-your-team-2jj1</link>
      <guid>https://dev.to/teamonly/how-to-share-an-app-you-built-with-ai-just-with-your-team-2jj1</guid>
      <description>&lt;p&gt;Last updated 25 October 2026. Written by TeamOnly. We make one of the options below, so prices and limits link to each vendor's own pages.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quick answer:&lt;/strong&gt; Put the app on a host that checks your company login before the app loads. Coworkers sign in with their work Google or Microsoft account, or a code sent to their work email, and nobody else gets in.&lt;/p&gt;

&lt;p&gt;Skip the public link with a password, and don't make everyone sign up for the tool you built it with. The rest of this page shows each option, the steps, and a five-point test for "private".&lt;/p&gt;

&lt;h2&gt;
  
  
  What are my options for sharing it privately?
&lt;/h2&gt;

&lt;p&gt;Here are the common routes, ours included. They differ in who can get in, whether coworkers need a new account, and how much you have to set up yourself.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Who gets in&lt;/th&gt;
&lt;th&gt;New account for coworkers?&lt;/th&gt;
&lt;th&gt;Database included&lt;/th&gt;
&lt;th&gt;Cost to make it private&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Public host + password (Vercel, Netlify, Replit)&lt;/td&gt;
&lt;td&gt;Anyone who has the shared password&lt;/td&gt;
&lt;td&gt;No, just the password&lt;/td&gt;
&lt;td&gt;Not on Vercel or Netlify. Replit has one built in&lt;/td&gt;
&lt;td&gt;Vercel: $20/mo per project on Pro. Netlify: Pro plan, $20/mo&lt;/td&gt;
&lt;td&gt;A short demo for someone outside the company&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The builder's private sharing (Lovable, Replit, Vercel Authentication)&lt;/td&gt;
&lt;td&gt;People with an account on that platform, in your workspace or invited&lt;/td&gt;
&lt;td&gt;Yes, on that platform&lt;/td&gt;
&lt;td&gt;Lovable and Replit: yes. Vercel: add one&lt;/td&gt;
&lt;td&gt;Lovable: Business plan, from $50/mo. Replit: Starter or Core and up. Vercel Authentication: free&lt;/td&gt;
&lt;td&gt;Teams where everyone already uses that platform&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cloudflare Access (in front of your own host)&lt;/td&gt;
&lt;td&gt;Your company login or an emailed one-time PIN, once you set it up&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No, it isn't a host&lt;/td&gt;
&lt;td&gt;Free to 50 users, then $7 per user a month, billed yearly&lt;/td&gt;
&lt;td&gt;Technical builders already running on Cloudflare&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Tailscale or a VPN (a private network)&lt;/td&gt;
&lt;td&gt;People connected to your private network&lt;/td&gt;
&lt;td&gt;Yes, everyone installs and signs in to the VPN app&lt;/td&gt;
&lt;td&gt;No, you run the server&lt;/td&gt;
&lt;td&gt;Depends on your VPN plan&lt;/td&gt;
&lt;td&gt;Companies where everyone already runs the VPN&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Internal tools platform (Retool and similar)&lt;/td&gt;
&lt;td&gt;Users you add to the platform&lt;/td&gt;
&lt;td&gt;Yes, a user seat&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Retool Team: $10 per builder and $5 per user a month, billed yearly&lt;/td&gt;
&lt;td&gt;Building in a visual builder instead of with code&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;TeamOnly&lt;/strong&gt; (a host with company login built in)&lt;/td&gt;
&lt;td&gt;Anyone at your company: work Google, work Microsoft or an emailed code&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes, one per app, plus file storage and secrets&lt;/td&gt;
&lt;td&gt;$19/mo for the builder. People who only use apps are free&lt;/td&gt;
&lt;td&gt;An app you built with Claude Code or Cursor that the team should use today&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Checked 25 October 2026. Sources: &lt;a href="https://vercel.com/docs/deployment-protection" rel="noopener noreferrer"&gt;Vercel Deployment Protection&lt;/a&gt;, &lt;a href="https://docs.netlify.com/manage/security/secure-access-to-sites/password-protection/" rel="noopener noreferrer"&gt;Netlify password protection&lt;/a&gt;, &lt;a href="https://docs.replit.com/cloud-services/deployments/private-deployments" rel="noopener noreferrer"&gt;Replit: who can access your app&lt;/a&gt;, &lt;a href="https://docs.lovable.dev/introduction/subscription-plans" rel="noopener noreferrer"&gt;Lovable plans&lt;/a&gt;, &lt;a href="https://www.cloudflare.com/zero-trust/products/access/" rel="noopener noreferrer"&gt;Cloudflare Access plans&lt;/a&gt;, &lt;a href="https://retool.com/pricing" rel="noopener noreferrer"&gt;Retool pricing&lt;/a&gt;. More detail: &lt;a href="https://teamonly.dev/compare?ref=devto" rel="noopener noreferrer"&gt;the full comparison&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do I share it with TeamOnly?
&lt;/h2&gt;

&lt;p&gt;Five steps, about ten minutes the first time. You need Node.js on your computer, which Claude Code and Cursor users already have.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Pick a plan with your work email.&lt;/strong&gt; Builder is $19 a month for one builder and up to three apps. Your company is set up when you pay, and your email domain becomes the door. &lt;a href="https://teamonly.dev/pricing?ref=devto#subscribe" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#subscribe&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run &lt;code&gt;npx teamonly init&lt;/code&gt; in your project.&lt;/strong&gt; It adds instructions that Claude Code and Cursor read, plus the small library your app uses for the signed-in person, the database and files.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask your AI tool for the app.&lt;/strong&gt; Plain English is fine: "Build an expense approval tool. People submit receipts, managers approve, finance marks them paid." The instructions keep it to a shape that runs on TeamOnly: a React front end and a small API.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sign in once, then deploy.&lt;/strong&gt; Run &lt;code&gt;npx teamonly login&lt;/code&gt; the first time on your computer, then &lt;code&gt;npx teamonly deploy&lt;/code&gt;. You get a link like &lt;code&gt;expenses.acme.teamonly.app&lt;/code&gt;. The database, file storage and secrets are created on the first deploy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Send the link.&lt;/strong&gt; Anyone at your company can open it. You can narrow it to named people with &lt;code&gt;npx teamonly access only dana@acme.com sam@acme.com&lt;/code&gt;.
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight console"&gt;&lt;code&gt;&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;npx teamonly init
&lt;span class="go"&gt;✔ Added instructions for Claude Code and Cursor
&lt;/span&gt;&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;npx teamonly login
&lt;span class="go"&gt;✔ Signed in as dana@acme.com
&lt;/span&gt;&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;npx teamonly deploy
&lt;span class="go"&gt;✔ Live at https://expenses.acme.teamonly.app
  Only @acme.com accounts can sign in.
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can also ask Claude Code or Cursor to run these for you. They ask before running anything. No Cloudflare account, no database service, no login code to write.&lt;/p&gt;

&lt;h2&gt;
  
  
  What will my coworker see?
&lt;/h2&gt;

&lt;p&gt;A sign-in screen with your company's name on it, then your app.&lt;/p&gt;

&lt;p&gt;They click "Sign in with Google" or "Sign in with Microsoft" and pick their work account, or type their work email and enter the 6-digit code we send. The app knows who they are by name. Next time, they are already signed in.&lt;/p&gt;

&lt;p&gt;Someone with a personal Gmail, or from another company, is turned away at that screen. Your app never loads for them. More: &lt;a href="https://teamonly.dev/company-login?ref=devto" rel="noopener noreferrer"&gt;company login&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why not just use a public link with a password?
&lt;/h2&gt;

&lt;p&gt;Most hosts are built for websites anyone can visit. Making one private for a team is an add-on, and it usually means a shared password.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The password travels.&lt;/strong&gt; It ends up in a chat thread or an email to a contractor, and you can't tell who has it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It has no names.&lt;/strong&gt; If everyone logs in the same way, the app can't record who approved an expense.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It doesn't leave with people.&lt;/strong&gt; Someone who leaves the company still knows it until you change it and tell everyone else.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unlisted is not private.&lt;/strong&gt; A link nobody was told about still gets found, shared and sometimes indexed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Vendor research: security company Red Access reported finding more than 380,000 publicly reachable assets on the main vibe-coding platforms. About 5,000 looked like company tools, and more than 2,000 of those held sensitive business or personal data. &lt;a href="https://thehackernews.com/2026/05/what-2000-exposed-vibe-coded-apps.html" rel="noopener noreferrer"&gt;Summary on The Hacker News&lt;/a&gt; (a contributed article, May 2026).&lt;/p&gt;

&lt;h2&gt;
  
  
  What does "private" have to mean for a work app?
&lt;/h2&gt;

&lt;p&gt;Whatever you choose, check these five things. Each one takes a minute.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The login comes before the app.&lt;/strong&gt; Nobody sees a single screen of the app, or gets any data out of it, until they have signed in. A page that loads first and then asks for a login is not private. &lt;em&gt;How to check:&lt;/em&gt; open the link in a private browser window. You should land on a sign-in screen. Try an address from the app's API too, like &lt;code&gt;/api/expenses&lt;/code&gt;. It should refuse you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Only company accounts get in.&lt;/strong&gt; People sign in with an account your company controls, and the email domain is checked on the server. Personal accounts are turned away. &lt;em&gt;How to check:&lt;/em&gt; try signing in with a personal Gmail or Outlook address. You should be refused.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Each app's data is kept apart.&lt;/strong&gt; The app has its own database, files and keys. Another app, or a stranger with the database address, can't read them. &lt;em&gt;How to check:&lt;/em&gt; ask whether anyone could reach the database without going through the app's login. With Supabase, check that row-level security is on for every table. Make sure no keys are written into the code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It doesn't show up in search.&lt;/strong&gt; Search engines are told not to list the app, and they can't see inside it anyway. &lt;em&gt;How to check:&lt;/em&gt; search for the app's address in Google. Check the response for a &lt;code&gt;noindex&lt;/code&gt; header.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Access ends when someone leaves.&lt;/strong&gt; When a person leaves the company, they lose access without you doing anything special, and nobody needs a new password. &lt;em&gt;How to check:&lt;/em&gt; if this person's work account were turned off today, could they still get in tomorrow? With a shared password, the answer is yes.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;With TeamOnly&lt;/strong&gt;, all five are handled for you. Sign-in is checked before any app code runs, on every request. Personal addresses are refused. Each app gets its own database, file storage and secrets. Every response says &lt;code&gt;noindex&lt;/code&gt;. Sign-in goes through the work account, so when it is turned off, new sign-ins stop; a session lasts at most 7 days, and taking someone off an app's list works on their next click. More: &lt;a href="https://teamonly.dev/security?ref=devto" rel="noopener noreferrer"&gt;security details&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  I built it in Lovable, Bolt, Replit or v0. Can I still do this?
&lt;/h2&gt;

&lt;p&gt;Start with the platform's own private sharing. If everyone on your team already has an account there, it may be all you need: Lovable's Business plan can limit a published app to your workspace, and Replit can publish to your workspace or to invited people.&lt;/p&gt;

&lt;p&gt;If your coworkers don't have accounts there, export the code. TeamOnly runs a React front end with a small JavaScript or TypeScript API. Apps that rely on Supabase for login and tables, or on Next.js server features, need changes first. Python apps can't run here. Email &lt;a href="mailto:hello@teamonly.dev"&gt;hello@teamonly.dev&lt;/a&gt; with what you have and we will tell you straight.&lt;/p&gt;

&lt;h2&gt;
  
  
  I built it in Claude Code or Cursor. What changes?
&lt;/h2&gt;

&lt;p&gt;Very little. Run &lt;code&gt;npx teamonly init&lt;/code&gt; in the project and ask your AI tool to fit the app to TeamOnly. It reads the instructions and uses our login, database and files instead of reaching for services we don't run.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/claude-code?ref=devto" rel="noopener noreferrer"&gt;Claude Code guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/cursor?ref=devto" rel="noopener noreferrer"&gt;Cursor guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/templates?ref=devto" rel="noopener noreferrer"&gt;Templates to start from&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Questions people ask
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How do I share an app I made with Claude Code with my coworkers?
&lt;/h3&gt;

&lt;p&gt;Host it somewhere that checks your company login before the app loads, then send the link. With TeamOnly that is &lt;code&gt;npx teamonly init&lt;/code&gt;, &lt;code&gt;npx teamonly login&lt;/code&gt; and &lt;code&gt;npx teamonly deploy&lt;/code&gt;. Coworkers open the link and sign in with their work Google or Microsoft account, or a code sent to their work email.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I keep a vibe-coded app private without putting it on the internet?
&lt;/h3&gt;

&lt;p&gt;Every web app is on the internet in the sense that it has an address. What matters is that nobody can use it, or read its data, without signing in with a company account first. A shared password or an unlisted link does not do that. A login in front of the app does.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do my coworkers need an account to use it?
&lt;/h3&gt;

&lt;p&gt;It depends on where you host it. Private sharing on Lovable, Replit or Vercel needs an account on that platform. Cloudflare Access and TeamOnly use the work account people already have. On TeamOnly, people who only use apps are free.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is a password on a Vercel or Netlify site good enough for a team?
&lt;/h3&gt;

&lt;p&gt;For a short demo, maybe. For a tool people use every day, no. The password gets passed around, the app can't tell who did what, and someone who leaves still knows it. It also costs extra: $20 a month per project on Vercel Pro, and a Pro plan on Netlify, as of October 2026.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I run it on my laptop and share the link?
&lt;/h3&gt;

&lt;p&gt;With a tunnel tool you can, but the app is off whenever your laptop is asleep, and the data lives on your machine. It is fine for showing someone a draft. For a tool the team depends on, put it on a host.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Cloudflare Access enough to protect an AI-built internal app?
&lt;/h3&gt;

&lt;p&gt;It is a strong login gate, free for up to 50 users. You still need to host the app, pick a database, connect an identity provider and write a policy for each app. If you are comfortable doing that, it is a good choice. &lt;a href="https://teamonly.dev/compare/cloudflare-access?ref=devto" rel="noopener noreferrer"&gt;TeamOnly vs Cloudflare Access&lt;/a&gt; goes through it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/compare/cloudflare-access?ref=devto" rel="noopener noreferrer"&gt;TeamOnly vs Cloudflare Access&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/compare?ref=devto" rel="noopener noreferrer"&gt;Every option, side by side&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/company-login?ref=devto" rel="noopener noreferrer"&gt;Company-only login&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/how-it-works?ref=devto" rel="noopener noreferrer"&gt;How it works&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://teamonly.dev/pricing?ref=devto" rel="noopener noreferrer"&gt;Pricing&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Get started: &lt;a href="https://teamonly.dev/pricing?ref=devto#subscribe" rel="noopener noreferrer"&gt;https://teamonly.dev/pricing?ref=devto#subscribe&lt;/a&gt; (Builder $19/mo, Team $249/mo)&lt;br&gt;
Not ready? Get updates: &lt;a href="https://teamonly.dev/waitlist?ref=devto" rel="noopener noreferrer"&gt;https://teamonly.dev/waitlist?ref=devto&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>security</category>
    </item>
  </channel>
</rss>
