No. We are building it now and opening early access to a small number of teams. Signing up starts a conversation, not a trial.
Those need you to define the trigger, every step, every condition and every error path in advance. That works for rigid processes and badly for everything else. Here you describe the job and the limits of authority, the way you would brief a colleague, and the employee works out the steps.
Not by default. Reading is allowed; anything that writes to a real system, sends an external message or touches money is classified by risk and asks for approval first. New employees start on probation, and every action lands in a worklog you can read back.
No, and that is deliberate. An employee's effective permissions are the intersection of your workspace policy, the user's role, the connected account's scopes and the employee's own tool policy. It cannot exceed the person who asked.
The EU. That is the baseline from the first release rather than an enterprise upsell. Credentials are never placed in the model's context — the employee sees a connection, never a token.
You pick two or three jobs that genuinely cost your team hours each week. We measure how long they take today, build those first, and check after a few weeks whether it actually helped. If it did not, we would rather know.
We have not set pricing. It will be a workspace subscription with usage included rather than a charge per employee you create — you should not be billed for describing a role. Early access participants will not be surprised by a bill.