Nekton

The clearest thing about Nekton is that it tells you what it is bad at. Most automation vendors publish a feature grid; Nekton publishes a two-column "Works well / Does not work well" table on its own homepage. That table is the most useful piece of information on the site, and it should shape how you evaluate the product. What it does: you describe your task step by step in plain English. If the task can be automated, Nekton writes the automation code and runs it in the cloud. The building blocks it names are Forms (collect input from users and use it in the automation), Sharing (send a link to your workflow so others can run it, no sign-up required), Schedules (run your workflow on a schedule), Integrations (the site claims Nekton can integrate with thousands of different apps and do anything using their API), Easy customizations, Automate gradually (mix manual and automated steps and automate as needed), and No maintenance (cloud execution, no infrastructure to set up). The plain-English authoring model is the real differentiator. Instead of assembling a logic tree, you iterate on a description until the automation does what you meant. That is a much gentler on-ramp than visual builders, and it is the reason someone who would never open Zapier might actually finish a workflow here. Where it fits: small, specific, cloud-to-cloud tasks with public APIs. Notify-me-when-someone-mentions-X, post news to Twitter, send a survey, create checklists, generate a report. These are exactly the tasks that are too small to justify a developer and too tedious to do by hand. Where it doesn't: the vendor's own list. Vague or complex goals, automation that must run locally, services that aren't reachable from the internet, and large data volumes. Treat that list as a hard boundary rather than a soft caveat — an AI that writes code from your description can only work with what it can reach from the cloud, and ambiguous descriptions are the failure mode you should expect, since you are describing intent rather than specifying steps. Other practical notes: workflows are shareable by link without the recipient signing up, which makes Nekton viable for one-off internal tools and simple customer-facing forms. Execution is cloud-only, which is what makes "no maintenance" possible but also rules it out for anything that has to touch private or on-premise systems. The site also advertises a partner program for people who enjoy building automations and want to earn income by sharing them. Our call: use Nekton as a personal and small-team productivity tool for narrow, well-specified cloud tasks. Do not treat it as a replacement for a full automation platform, and do not expect it to handle a job that hasn't been thought through yet.