What Toolcrow does not do

No server code

• A drop has no server of its own. Server-side code (Node.js servers, Express, Next.js API routes, PHP, Python, Flask) does not run on Toolcrow. Projects that need a build step (for example a Vite project with package.json) are not built; only static files and single components are served.
• Saving data, AI calls and feedback are what Toolcrow offers in place of a server (see Saving data, AI inside a drop, Feedback and Nest). There is no general database, no scheduled tasks and no sending of email from a drop.

No email when a submission arrives

Toolcrow does not email the maker when a visitor saves a submission. New submissions show up on the Submissions page, or in the connected Google Sheet. A notification rule set in that Sheet does not help: Toolcrow writes with the maker's own Google account, and Google does not send notifications about your own changes. To get a message for each new submission, forward submissions to Slack, Discord or Microsoft Teams, or to Zapier, Make or n8n to send an email or anything else from there (see Saving data).

Secret keys stay out of a drop's code

• A drop runs in the visitor's browser, so anyone who can open it can also read its code. That is true for every website that runs in the browser, not something specific to Toolcrow. An API key, password or token written into the code can be copied by any visitor.
• For what Toolcrow provides, the code needs no key. AI calls go through Toolcrow's AI proxy, and the key stays on Toolcrow's server (see AI inside a drop). A connected Google Sheet is reached through Toolcrow as well, and the access to it is stored encrypted on Toolcrow's side (see Saving data).
• A webhook address works like a key: whoever has it can post to it. Forwarding submissions keeps the address encrypted on Toolcrow's side, so the drop's code never contains it (see Saving data). A tool that posts to a webhook from its own code has the address in its code instead.
• Toolcrow does not store keys for other services. A tool that talks to a service with the maker's own secret key (for example Airtable, Notion or a payment provider) would have that key in its code, readable by visitors.
• Connecting such a service through Toolcrow, so a drop can read from it or write to it without a key in its code, is not available yet. The Connections page only lists connectors that work today; "Suggest a connector" there tells Toolcrow which service a maker needs. Sending submissions to a service already works without a key, also to Airtable and a HubSpot form (see Saving data).

No custom domains, no search engines, no embedding

• Drops are served on toolcrow.live addresses. Custom domains are not supported.
• Drops are kept out of search engines on purpose (noindex).
• Drops cannot be embedded in other websites in an iframe; only Toolcrow itself shows them in a frame.
• The "Powered by Toolcrow" badge cannot be switched off.

No visitor accounts

Visitors do not sign in to a drop. Access is controlled with the link, a password or the private setting (see Sharing and access). There are no per-person accounts or permissions for visitors.

Nothing published without the maker

A connected AI can read, propose and create private drops, but never publishes or shares, changes settings or reads visitors' data (see Connecting your own AI). Automatic adjustments after deploy only keep a tool's data per visitor; Toolcrow never starts collecting or sharing visitors' data on its own (see Saving data).

File types

Markdown is not an input format, and new PowerPoint files are not accepted (export to PDF instead). See Building and importing.