Each task runs in its own workspace.
Code execution, application processes, and connected services stay separated from other tasks.
SECURITY
Run software tasks with clear boundaries and full visibility.
Rubic runs each task in an isolated workspace, uses only the project resources your team connects, and keeps code changes, checks, logs, and approvals available for review.
TASK EXECUTION
Rubic separates the work and shows what it changed.
No vague trust claims. These are the concrete boundaries teams can see while Rubic works.
Repository access follows the active project.
Rubic works only with the repositories and project resources your team has connected.
Runtime values stay attached to the task.
Teams can configure task environment values without adding them to repository files or public previews.
Branches and pull requests stay reviewable.
Rubic works on a task branch, records changed files, and opens a pull request for delivery when code changes are required.
Live previews are temporary and task-specific.
Preview resources are created for the task, exposed through a dedicated address, and removed when no longer needed.
The work remains visible while it runs.
Task messages, changed files, checks, application logs, and delivery state stay together for review.
HUMAN CHECKPOINTS
Your team can review the work before it moves forward.
Approval behavior is configured per task. Teams can review the plan, answer questions, request revisions, inspect the running application, and decide when a pull request is ready to merge.
01 Approve the implementation plan Before coding
02 Answer product or technical questions During work
03 Review changed files, checks, and the live app Before delivery
04 Approve and merge the pull request At delivery