Secure remote actions for software teams

Ract

Ract is an early-stage project exploring a simple idea: run selected sensitive or restricted build and release steps on controlled machines while keeping the calling environment clean and the workflow developer-friendly.

  • Active development
  • Working prototype
  • Not publicly available

PS> ract sign MyApp.exe

Submitting sign action...

Action completed successfully

Signature verified

MyApp.exe

Current prototype example — command syntax and output may change.

Development status

An active project, not a released product

Ract is being designed and tested, but there is no public download or release date. Commands, components, supported environments, and capabilities may change as the project develops.

Why Ract is being developed

Give sensitive actions a controlled place to run

Some build and release steps need credentials, specialized tooling, or a tightly controlled environment. Ract is exploring a focused way to invoke those steps without recreating that environment everywhere.

Isolate sensitive actions

Run selected operations on machines prepared and controlled for that purpose.

  • Separate sensitive steps from everyday systems
  • Keep specialized tooling in a known environment
  • Define clear boundaries around each action

Keep credentials where they belong

Reduce the need to place sensitive credentials on every calling machine.

  • Call actions from development or CI workflows
  • Keep protected resources on controlled systems
  • Avoid duplicating sensitive setup unnecessarily

Make the workflow repeatable

Invoke a defined action consistently without turning every caller into the action host.

  • Developer-friendly command-line interaction
  • A consistent place for configured actions
  • A direction suitable for local and CI use

The first proof point

Starting with remote code signing

Remote code signing is the first workflow being used to validate Ract. The prototype has already processed and verified real build artifacts end to end, including files produced by InSpace Software's own build process.

  • Submit the action using a concise CLI command
  • Run signing in a controlled environment
  • Return the signed build artifact
  • Verify the resulting digital signature

Current answers

Frequently asked questions

These answers describe the project as it exists today without promising its final shape.

What is Ract?

Ract is an early-stage project exploring a controlled way to run selected development or release actions on dedicated machines instead of placing every tool and credential on a developer workstation or CI runner.

Is Ract available to download?

Not currently. Ract is in active development and prototyping. It is not yet available as a public download or commercial product.

What is being tested first?

Remote code signing is the first concrete workflow being used to develop and validate the idea. The current prototype has successfully signed real build artifacts end to end.

When will Ract be released?

There is no public release date. The priority is to validate the core workflow and make it dependable before making availability or timeline commitments.

Will Ract be self-hosted?

The current direction is to keep Ract self-hostable so actions can run on machines controlled by the user. If hosted components are introduced later, they will be optional and clearly communicated.

Can I share a use case or follow development?

Yes. Visit the dedicated Ract website for the latest public information, or contact InSpace Software with a short description of your workflow and environment.

Interested in the direction?

Follow Ract as it develops

Visit the dedicated website or share a relevant development and release use case.