Trust

It does exactly what you asked.

Faber runs the actions you approved, in the order you approved them. You see a full preview run before it goes live, and a plain record of everything it did after.

It follows your words

You wrote the steps. It sticks to them.

Faber runs the exact steps you wrote, in the same order, on every run.

It doesn't wander off task or get creative between runs.

Before anything goes live, you see a full preview run: every action, nothing sent.

You choose which actions need your approval; the rest run on their own.

Every run

Three things stay true on every run.

What you approved is what runs

Same actions, same order, run after run. Only the mail and the rows change.

You stay in control

It uses only the accounts you connect, and you choose what needs your approval. Disconnect any account anytime.

Nothing hidden

Every run leaves a plain record of what it checked, did, set aside, and skipped.

How it's enforced

A task can only reach what you gave it.

Its own locked-down process

Every run happens in a fresh process of its own, started with a specific list of what it may touch. Nothing carries over from the last run.

Only the services you connected

That list names the services the task actually uses. A task you never connected to Slack cannot reach Slack, even if something went wrong and it tried.

Only its own files

It can read and write the files belonging to that task and nothing else on the machine. Its sign-in details are scoped the same way, one task at a time.

For the technically minded

The specifics.

Each run starts fresh. The task's own code runs in an isolated JavaScript environment that holds no sign-in details and cannot open a network connection. Every call it makes to a connected service is handed to the part of the run that holds that task's credentials, which can reach only the hosts those connections need. Anything outside that list is refused by the runtime itself, not by our code.

On Faber Cloud the operating system enforces it as well: the task's code runs in a separate process that has an empty environment, cannot open a socket, and can read none of the server's files. Each run starts from a clean temporary directory, with every task file verified against its checksum before it executes. Nothing is reused between runs.

Your connections stay protected.

You connect only the accounts you approve, credentials are stored encrypted, and our privacy and security practices are public.