Ways to run it
One product, two ways to deploy.
The scheduling engine, the analysis and the change controls are the same in both. What changes is who uses it and where it runs.
Standalone
One user, on your own machine. Available
SchX runs on a Windows laptop or desktop. It is a lightweight local setup, not a full server install.
Scheduling, the Arc engine, analysis, the Gantt, DCMA checks and risk all work fully offline, and your schedule data stays on the machine.
Standalone is for a single user. For more than one user, use the team deployment.
What works offline
- Scheduling with the Arc engine
- Schedule analysis and DCMA 14-point checks
- The Gantt and the schedule views
- Risk models and Monte Carlo runs
AI models and MCP connectors are optional. If you turn them on, your IT team allows the firewall access they need.
Team
Multi-user, deployed as a server.
For planning teams and organizations. SchX runs as a server, much like enterprise scheduling systems that many people use at once, and your team works through the web application.
Your private cloud or data center
Deploy SchX on a Linux virtual machine in your own environment, from a versioned release with a documented install and forward-only upgrades.
Major cloud providers
Deployment on a major cloud hosting provider such as AWS or Azure.
Hosted web version
SchX hosted for you, so your team only needs a browser.
Shared projects
Up to 10 people edit the same project at once, with live updates, record locks and version-checked saves.
Roles
Viewer, Statuser, Planner, Scheduler and Project Admin, set per project and per user group, and checked by the server on every request.
Admin controls
Accounts, groups, licenses, AI providers and access, the secret vault, backups, the support bundle and the audit trail, all in Admin.
See the Teams page for collaboration, security and administration in detail.
AI models
Modular and replaceable.
The assistant is optional. Scheduling, the Arc engine, analysis, the Gantt, DCMA checks and risk all work with AI switched off.
The model is a component, not the product. You can change it without touching the engine that produces the numbers.
- Chosen in Admin settings. Available Administrators pick local models, private models, or frontier cloud models through API access, such as Anthropic or OpenAI.
- Denied by default. Available AI network access is off for every workspace until an administrator turns it on.
- Standalone firewall access. Available In the standalone version, your IT team allows firewall access for whichever model option you choose. The same applies to MCP connectors.
MCP connectors
Connect outside AI tools, on your terms. Available
MCP, the Model Context Protocol, is an open standard that lets AI tools call another system's functions in a controlled way. SchX has its own MCP server, so outside AI tools and other systems can work with your schedules through SchX's engine and SchX's rules.
Reader
Read only. Questions, tracing and analysis across the schedule. Nothing can change.
Proposer
The 46 read tools plus 23 that stage changes for review. Only one assistant stages changes in a workspace at a time.
Apply
Approving, applying and exporting are blocked for outside tools. The server refuses them before anything runs. Only a planner approves and applies changes.
Controlled access
- OAuth sign-in with read or propose scopes
- Scoped per account and per workspace, with a tool allow-list per client
- Rate limited
- Revocable at any time, effective on the next request
- Connector clients managed by administrators in Admin settings
- Every call logged in the audit trail
Who sets it up
- Team deployment. The administrator sets up connectors on the server.
- Standalone. Your IT team allows the firewall access the connector needs.
- Cloud AI clients. Claude, ChatGPT and other cloud clients connect to SchX and its P6 tools through MCP, with the same permissions and safety as a connection on your own network.
The SchX MCP server has 85 tools in all: the 46 read tools, the 23 staging tools, and 16 that approve, apply, export or administer. Those 16 are refused for outside tools and are used only by planners and administrators inside SchX.