Earlier Core documentation

Looking for the systems behind Arcturus?

Start with our current technology and product manuals. This earlier Core documentation is kept below as a reference, separate from the current systems product pages.

Read the original Core documentationProduct previews and business briefs | Valen Systems

Product previews and business briefs

Applies to: Public Core prototype

Updated

Core presents product environments as work that can be explored in context. The public prototype includes representative interfaces as well as conventional company information. Read each environment's description before interpreting an available control as a connection to a live system.

Rubian and Kestowv#

The Rubian/Kestowv preview introduces command work, system inspection and operational state within Core. The public rendition does not provide access to a visitor's computer or an attached enterprise host.

For a provisioned operating environment, use Rubian/Kestowv Documentation. That manual describes the commands and pilot procedures available in the supplied products. A command shown in the prototype is not an installation instruction.

Arcturus and Valux#

Arcturus is reliability and management software built on Rubian and Kestowv, spanning individual machines, home clusters, fleets and data centers. Valux is the broader operating-system research connecting the operating environment, systems foundation and interface work.

The current Arcturus rendition lets you inspect representative conditions and operational work. The Arcturus guides cover those data-center and machine demonstrations; Valux documentation explains the broader operating-system research. Opening an Early Access view does not install Arcturus or an operating system.

Get Core and Get Valen#

Get Core concerns a business system centered on the programmable interface: what people should see, decide and do, and which applications the interface must connect. Get Valen concerns a system centered on Valen's role in the work. These are distinct starting points for defining an engagement.

The brief form asks for Business description and System needs. Use Save brief on this device to retain a draft locally. The confirmation states that it has been saved on the device; it has not been submitted as a request. Clear saved brief removes that local draft.

To discuss a project, use the company's contact page. Review any request or commercial terms at that destination before submitting. Saving a brief in Core does not create a purchase or a software license.

Other product views#

Tools such as mail, customer-work management or a model workspace may appear as Core product renditions. Their visible workflow helps describe the intended experience. Actual account access, outbound delivery, persistence and connected operations depend on the attached product and its documented environment. Use the displayed connection and action result to determine what is available.