A description of Tachyon Stacks and their Tachyon components, the Tachyon clients and how they connect to provide the Tachyon features.

Tachyon deployment architecture

At the top-most level, Tachyon architecture consists of Tachyon Server components, grouped into Stacks, and clients that are deployed onto the devices that you want to manage.

Tachyon client and its features are part of the 1E Client.

Tachyon Server Stacks

Every Tachyon system has a single Master Stack, which provides web services for Tachyon applications. Master Stack components are typically all installed on a single Master Server.

Tachyon real-time features require Response Stacks, which are made up of one or more Response Servers. A DMZ Server is an example of a Response Server. Each Response Stack has at least one Background Channel for sharing resources, and a single Core component that supports an associated set of up to five Switches. Switches are the primary mechanism for rapidly requesting and retrieving responses from the Tachyon clients. As each Switch can handle up to 50,000 devices there is a limit of 250,000 devices per Response Stack. Higher numbers can be achieved if you contact 1E for guidance. Switches may be local or remote to the other components in the Response Stack.

Databases for Tachyon, Catalog, Content Distribution, Experience, SLA and BI, are installed on SQL Server database instance(s) that may also be local or remote to their respective Master and Response servers. It is also possible for multiple Response Stacks to share the same Responses database. The Cube used by Patch Success (SLA-BI) is installed on a local or remote SQL Server Analysis Services (SSAS) instance.

Please refer to Design Considerations: Tachyon Architecture section for guidance on which architecture to choose. Below is a detailed description of Tachyon components.

Please refer to Communication Ports reference page for connection details between components and ports necessary for firewalls.

On this page:

Tachyon Single-Server system

In the most basic setup there is a single server which hosts both a Master Stack and a Response Stack and this can be deployed by selecting the default settings in Tachyon Setup

The following table shows the Tachyon Platform components, including Tachyon Master and Response Stacks, and also shows the DMZ Server discussed in Tachyon architecture for Internet-facing devices.

SubsystemComponentWeb applicationMaster StackResponse StackDMZ Server
Master ServerTachyon Portal UI and Tachyon applicationsTachyon1

Consumer APIConsumer1

Coordinator service

Tachyon Master database
1 (optionally Remote)

ExperienceExperience APIExperience1

Experience database
1 (optionally Remote)

Content DistributionContent Distribution APIContentDistribution1 (optional)

Content Distribution database
1 (optionally Remote)

1E CatalogCatalog UICatalogWeb1

Catalog APICatalogWeb

Catalog Update Service

Catalog database
1 (optionally Remote)

SLA and InventorySLA Platform UI and SLA applicationsPlatform1

SLA Admin


SLA Engine

SLA Integrate services:

  • SLA Integrate Agent service
  • SLA Integrate Manager service


SLA Operations Provider APICoreExternal1

SLA databases (Data, Integrate, Shared)
1 (optionally remote)

SLA Business Intelligence (BI)

(for Patch Success)


SLA-BI database
1 (optionally Remote)

SLA-BI cube (requires SSAS)
1 (optionally Remote)

Response ServerCoreCore
Background ChannelBackground
Switch(es) (also includes a single Switch Host service)

up to 5 (optionally Remote)up to 5
Tachyon Responses database

1 (optionally Remote)

The picture opposite shows a Tachyon Single-Server System with databases optionally installed locally or on remote SQL Server instance(s). Components colored green are optional in a Tachyon system.

The Response Stack has can be installed on the same server as the Master Stack, and on remote servers.

The DMZ Server has only the Tachyon client facing components of the Response Stack: the Background Channel and Switches.

Applications and Tools

Tachyon applications and tools are consumers, and all consumers connect to the Tachyon Consumer API. 

The following consumer applications run on Tachyon Platform and are installed using Tachyon Setup. See Design Considerations: License requirements for consumer applications.

Applications are categorized as follows:

  • Configuration - applications required to configure Tachyon Platform and required by all other applications
  • Client - applications that communicate with devices in real-time
  • Inventory – applications that use inventory features

Applications that are included in the Tachyon Platform license

Inventory 8.1View and export inventory, and manage associations.Inventory, configuration
Settings 8.1Configure and monitor platform features.Configuration
Guaranteed State 8.1Ensure endpoint compliance to enterprise IT policies.Client

Tachyon Explorer 8.1

Investigate, remediate issues and manage operations across all your endpoints in real-time.Client

Applications that require a license

AppClarity 8.1Manage software license compliance, License Demand Calculations, license entitlements, and for reclaiming unused software.Inventory
Application Migration 8.1Intelligently automate the migration of applications during a Configuration Manager OS deployment.Inventory
Nomad 8.1

Manage content distribution across your organization using a centralized dashboard.

1E Client requires Tachyon and Nomad features to be enabled on all clients.

Patch Success 8.1

Reports on and ensures successful patching of your enterprise.

Requires SLA Business Intelligence to be installed by Tachyon Setup, as described in Design Considerations: Business Intelligence. It also needs connectors to get meta-data for patches from whichever of the following that you use to approve patches:

  • Configuration Manager (SCCM) if it is configured to manage WSUS
  • Windows Server Update Services (WSUS).
Tachyon Experience 8.1Measure performance, stability and responsiveness for applications and devices to assess user experience across your enterprise.Client
The following types of application require 1E Client (with Tachyon features enabled) to be deployed to all in-scope devices.

  • All Client applications
  • Inventory applications if you intend using the Tachyon connector to populate your inventory.

The AI Powered Auto-curation feature is optionally used by Inventory applications to provide automatic curation of new products. This avoids having to manually add products to the 1E Catalog, or wait for it be updated. This optional feature requires additional memory on the Tachyon Server (Master Stack). Please refer to AI Powered Auto-curation: Memory requirements for details.

Some benefits of using AI Powered Auto-curation are that you can:

  • Achieve significantly more normalized software from the first sync
  • Reduce the manual effort required to normalize software
  • Get an expanded SAM offering as more data is available for AppClarity
  • Get additional coverage for Application Migration
  • Identify more software to review for security threats.

Tachyon Tools

The following are tools included in Tachyon Platform 8.1. These tools are not installed using Tachyon Setup. They have either their own installers or are included in download zips.

  • Tachyon ConfigMgr UI Extensions - installed as part of the Tachyon Toolkit, this is a right-click extension for the Configuration Manager console that providing the option to browse and run an instruction on devices in a specified Collection
  • Tachyon Run Instruction command-line tool - installed as part of the Tachyon Toolkit, it is used for sending instructions to the Tachyon server from a script or from a command prompt
  • Tachyon Product Pack Deployment Tool - included in the Tachyon Platform zip ProductPacks folder
  • Tachyon Instruction Management Studio - used for development of Tachyon instructions using the Tachyon SDK.

A typical Tachyon license allows use of all these tools.

Tachyon Multi-Stack system

The picture opposite shows a Tachyon Multi-Stack System. Here the Tachyon Master Stack communicates with one or more Tachyon Response Stacks. A local Response Stack is not mandatory. Components colored green are optional in a Tachyon system.

As with a single-server system, the databases are optionally installed locally or on remote SQL Server instances(s).

Tachyon components

Let's take a look at each of the Tachyon components in slightly more detail.


IIS Components

The following components are IIS Web Applications that reside on a single-server. Other configurations - such as Response Stack and DMZ Server - have a subset of these.

Under the Tachyon website:

Web ApplicationsApplication Pools
  • Admin (SLA Admin)
  • Background (Tachyon Background Channel)
  • CatalogWeb
  • Consumer (Tachyon Consumer API)
  • ContentDistribution (Nomad)
  • Core (Tachyon Core)
  • CoreExternal (SLA Ops Provider API)
  • Experience (optional)
  • Platform (SLA Platform UI)
  • Tachyon (Tachyon Portal UI)
  • CatalogWeb
  • ContentDistribution
  • SLAPlatform.Admin
  • SLAPlatform.CoreExternal
  • SLAPlatform.Platform
  • Tachyon.Background
  • Tachyon.Consumer
  • Tachyon.Core
  • Tachyon.Experience
  • Tachyon.Portal


The Core is a Tachyon Response Stack component which provides internal API and data processing.

Core does the following:

Background Channel

The Background Channel is a Tachyon Response Stack component which provides a means for the Tachyon clients to retrieve large data items from Tachyon without loading the Tachyon Switch:

  • Stores Tachyon content provided by the Consumer API in the Background Channel for Tachyon clients to retrieve
  • Responds to Tachyon clients retrieving Tachyon content from the Background Channel


The Switch is a Tachyon Response Stack component which provides the following:

The Switch Host service is responsible for starting local Switches.

Tachyon Portal UI

Tachyon users browse to the Tachyon Portal to access Tachyon applications.

Applications that are Tachyon built-in applications:

  • Guaranteed State
  • Inventory
  • Settings
  • Tachyon Explorer

Applications that are optional:

  • AppClarity
  • Application Migration
  • Patch Success
  • Tachyon Experience

Tachyon Consumer API

The Tachyon Consumer API provides the following:

  • Processes the consumer requests from the Explorer and other Consumers
  • Publishes Tachyon content to the Tachyon Background Channel
  • Forwards requests for instrumentation data from the Explorer to the Tachyon Instrumentation component
  • Forwards workflow commands from the Explorer to the Tachyon Workflow component

Tachyon Coordinator

The Coordinator service is the coordinating service used by Tachyon components. It has two modules, Workflow and Instrumentation.

The Workflow module provides the following:

  • Forwards workflow commands from the Consumer API to the Core
  • Stores workflow in SQL
  • Connects to remote SMTP to send emails used in the approval process for actions
  • The Workflow component contacts the Authentication component to manage the two-factor authentication process

The Instrumentation module processes instrumentation data from the following components:

  • Core
  • Workflow
  • Switch

And responds to requests for instrumentation data from the Consumer API.

Supports the two-factor authentication feature, with email.

Content Distribution

Content Distribution replaces the Nomad features of ActiveEfficiency Server, which is deprecated. Legacy Nomad clients continue to be supported by direct communication with the Content Distribution API, whereas Nomad 8.x clients communicate with the Content Distribution API via the proxy feature on Response Servers.

Tachyon Setup is used to install Content Distribution, and the Nomad app, and no longer installs ActiveEfficiency.

Nomad uses Content Distribution for the following features:

Catalog UI

The Catalog website used to view and interact with the Catalog.

Tachyon Setup supports installation of 1E Catalog on the Tachyon Master Stack server. For customers that want to continue using an existing installation of 1E Catalog 2.0 then Tachyon Setup supports using a remote Catalog server as a custom setup option. Please contact 1E for details of how to use custom setup options.

Catalog Update Service

Service used to connect to the 1E Cloud Catalog in order to download the latest catalog entries.

Catalog API

Consumer API used to manage and update the 1E Catalog.

SLA Admin

Internal API used to manage SLA components.

SLA Platform UI

The website used to view and interact with the Inventory.

SLA Engine

The Engine service is the coordinating service used by SLA components. This includes processing of Management Groups.

SLA Integrate Services

The SLA Integrate Agent sevice performs Connector functions by connecting to data sources and importing data into repositories.

The SLA Integrate Manager service manages Agent operations including repository action schedules.

SLA Inventory

The inventory repositories. Each instance of a repository is stored in SLA-Data database, and is based on a template defined in the SLA-Data database.

SLA Operations Provider API

Consumer API and functions used by SLA clients, including Application Migration task sequence steps and AppClarity Software Reclaimer.


Internal API used by Patch Success application.

Business Intelligence is an optional component installed by Tachyon Setup on the Master Stack, and requires SQL Server Analysis Services (SSAS). Business Intelligence is a prerequisite for the Patch Success application to support efficient presentation of visualizations on a large scale.

Consumer applications

The following Consumer applications are licensed:

  • AppClarity
  • Application Migration
  • Guaranteed State
  • Nomad (and Content Distribution)
  • Patch Success
  • Tachyon Experience
  • Tachyon Explorer

The following Consumer applications are included with Tachyon Platform:

  • Inventory
  • Settings

Other Tachyon Consumers are Tachyon Configuration Manager Console extensions, and other toolkit features.

SQL Server (Database Engine and Analysis Services)

Tachyon has two databases:

  • Tachyon Master
  • Tachyon Responses

Experience has one database:

  • TachyonExperience

Catalog has one database:

  • 1ECatalog

SLA has three databases:

  • SLA-Data
  • SLA-Shared
  • SLA-Integrate

SLA BI has two databases:

  • SLA-BI database
  • SLA-BI cube on a SQL Server Analysis Server (SSAS) instance

Nomad has one database:

  • ContentDistribution

1E Client

1E Client includes clients for: Tachyon, Nomad, PXE Everywhere Agent, Shopping/WSA, and WakeUp.

All the above are supported on Windows devices. Tachyon client features (excluding Experience and User Interaction) are also available on non-Windows devices.

Tachyon clients communicate with the Tachyon Switches and the Background Channel to provide responses to instructions (questions and actions) and subscribe to policy events for Experience and Guaranteed State. 

Nomad clients use Tachyon Switches and the Background Channel as a proxy for communicating with the Content Distribution.

Tachyon architecture for Internet-facing devices

Enabling Tachyon to support devices that are external to your company network is done by slightly extending the default single-server architecture.

The Responses Stack handles communications between the Master Stack and the Tachyon clients. The Background Channel and Switches components handle the direct communication with the Tachyon clients, the Core processes the information in both directions between the Master Stack and the Switches.

To enable external Tachyon client devices to interact with Tachyon you need to put the Background Channel and at least one Switch into the DMZ.

First, you need a working Tachyon system with a Response Stack that will provide the Core for the DMZ Server. The picture opposite shows a Response Stack and Master Stack on the same server, located on the internal network. This serves clients when they are connected to the internal network.

Then configure the internal firewall to allow two-way communication between each of the following:

  • The Core on the Internal Response Stack and the Switch(es) in the DMZ
  • The Coordinator on the internal Response Stack and the Switch(es) in the DMZ
  • The Consumer API on the internal Master Stack and the Background Channel in the DMZ

Configure the external firewall to allow incoming connections for:

  • The external Tachyon clients and the Background Channel in the DMZ
  • The external Tachyon clients and the Switch(es) in the DMZ

After you have provisioned a server in the DMZ, you need to make the following changes in the existing Tachyon system:

  • Run Tachyon Setup on the Tachyon Response Stack to tell it about the DMZ Server, which will do the following:
    • prepare the Master database with relevant details of the DMZ Background Channel and Switch(es)
    • raise the security level of the Core and Switch communications
    • produce a configuration file for the DMZ Server
  • Run Tachyon Setup on the DMZ Server using the pre-prepared configuration file, to complete the installation of DMZ Background Channel and Switch(es)

Detailed steps for the above process can be found on the Implementing a Tachyon DMZ Server page.

The DMZ picture shows a dual firewall design, but single firewall is also supported.

In the picture, components colored green are optional in a Tachyon system.