Each task runs in its own workspace.
Rubic separates code execution, application processes, and connected services from other tasks.
SECURITY
Run software tasks inside clear boundaries.
Rubic runs each task in a separate workspace. It uses only the project resources your team connects. Your team can review code changes, checks, logs, and approvals.
TASK EXECUTION
Rubic separates the work and shows what it changed.
See the specific boundaries that apply while Rubic works.
Repository access follows the active project.
Your team connects repositories and project resources. Rubic uses only these resources.
Runtime values stay attached to the task.
Your team can set runtime values for each task. These values do not need to be in repository files or public previews.
Branches and pull requests stay reviewable.
Rubic uses a task branch and records each changed file. It opens a pull request when the task changes code.
Live previews are temporary and task-specific.
Rubic creates a dedicated preview for the task. It removes the preview resources when you no longer need them.
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.
Set approval rules for each task. Your team can review the plan, answer questions, and request changes. It can inspect the running application and decide when to merge the pull request.
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