Frugent offers two distinct benefits: an existing website action map can make your first run cheaper, even if you have never run the task before. Repeat tasks can then follow saved, deterministic steps. Choosing where an automation runs changes who provides the browser, how it connects to accounts, and what infrastructure you pay for. Start with where your workflow already works.
The Action Map Registry is the collection; Frugent finds a compatible action map inside it and executes that map. Without a compatible map, setup and validation are needed first. Deterministic steps do not guarantee identical outcomes when a website or account state changes.
Local execution uses your own browser
A local browser runs on your computer. Your machine needs to be available while the automation executes. This can suit interactive workflows where you want to watch the browser and manage the connected account yourself.
Local does not mean every part of the system is offline. Frugent uses a service to coordinate connected devices and record run status. Review the data that your workflow sends before using it with sensitive information.
Cloud execution moves the browser to hosted infrastructure
A cloud browser uses compute supplied by the service. It can make sense for workloads that should not depend on a personal machine, but introduces hosting costs and requires a separate approach to authentication and account state.
Frugent cloud browser access is available by beta request. Cloud usage is separate from local subscription allowances; requesting access does not purchase cloud compute.
Choose the simplest place to start
Use local execution when your workflow belongs on your machine. Request the cloud beta when hosted execution is a requirement. Compare the local plans and connect a browser before expanding a workflow.