One foundationFiles, profiles and workspaces stay under the same OrbitFS system.
OrbitFS main system
One system for your files, profiles, workspaces and connected workflows.
OrbitFS is a modular working environment built around one consistent source of project information. Base organises the core system; add-ons extend it for connected context, sorting, conversion, documents and journal workflows without turning every job into a separate disconnected app.
Base systemWorkspace drivenProfile awareModular add-ons
ORBITFS SYSTEMCONNECTED
BaseCORE SYSTEM
FILESstructure + content
PROFILESreusable context
WORKSPACESproject focus
MCPconnected clients
APEXsort + convert
STUDIOcreate + edit
COREBase stays centralADD-ONSExtend the workflow
Context that carries forwardReuse organised information instead of rebuilding project context for every tool.
Focused add-onsAdd specialist capability only where the workflow needs it.
OrbitFS Base
The core system everything else works from.
Base is not just a launcher for add-ons. It is the working foundation: the place where files, profiles, workspaces, project structure, permissions and system-level controls stay organised.
Core systemBASE
Keep the source information stable while the workflow changes around it.
Instead of giving every project or add-on its own isolated copy of the same information, OrbitFS Base keeps the underlying material together. Workspaces decide what is relevant, profiles keep reusable context available, and add-ons operate around that shared foundation.
FILES→WORKSPACE→CONTEXT→WORKFLOW
FL
Files & structure
Keep documents, source material and working files organised inside the OrbitFS structure instead of scattering project information between unrelated tools.
PF
Profiles & reusable context
Maintain person, project and system profiles that can be reused across workspaces and connected workflows without rebuilding the same context every time.
WS
Workspaces
Create focused working areas for different projects, choose what each workspace loads, and keep project-specific information separate while still using one OrbitFS foundation.
PM
Permissions & management
Control who can view, edit and manage system areas, profiles, files and commands while keeping system-level and workspace-level roles distinct.
Workspace driven
Load what matters for the project you are actually working on.
OrbitFS workspaces let the same Base system behave differently for different projects without duplicating the whole environment.
Core information
Choose files or folders that should always be available when a workspace starts, including the core context the project depends on.
Conditional material
Keep supporting files and reference material available without forcing every item into every session or workflow.
Status & permissions
Define whether material is active, final, editable, locked or permission-controlled while keeping the workspace configuration understandable.
Same project, more capability
Connected add-ons work from the workspace context rather than building a second project model beside OrbitFS.
OrbitFS add-ons
Specialised systems that extend Base without replacing it.
Each add-on has a specific job. They are designed to use the same OrbitFS project structure and context rather than becoming separate islands of information.
01
Connected context
OrbitFS MCP
The connection layer between OrbitFS and supported AI or MCP clients.MCP makes the information already organised in OrbitFS available where you are actually working. It can load the right workspace, profiles and project context, expose approved OrbitFS commands and keep client sessions aligned with the same source information instead of manually rebuilding context in every conversation.
Workspace and project startup Profile and context loading Supported client connections OrbitFS commands and tools Reusable project context
02
Sort & convert
OrbitFS Apex
The ingestion, sorting and conversion layer for incoming material.Apex takes raw or incoming material and prepares it for OrbitFS. It can classify content, convert supported formats, organise output and route prepared material into the structure your workspace expects, reducing the amount of manual sorting required before the information is useful.
Incoming-file sorting Format conversion Classification and preparation Structured output Workflow routing
03
Create & edit
OrbitFS Studio
The focused document and journal workspace built around OrbitFS context.Studio gives document-heavy workflows a dedicated surface without disconnecting them from the rest of OrbitFS. It can work from the same files, profiles and workspace context, then create or update documents and journal-style content that remains part of the wider OrbitFS environment.
Document workflows Journal workflows Context-aware creation Editing and refinement OrbitFS-connected output
How OrbitFS works
Organise once, then let each workflow use the same foundation.
The system is designed so the core project information survives changes in tools, clients and workflows. The add-on changes; the foundation does not.
01
Organise the core
Base holds the files, profiles, workspaces and project structure that define the source information for the rest of the system.
02
Choose the workspace
A workspace decides what is relevant for the current project: which files load, which profiles matter, what is editable and what stays available only when needed.
03
Use the right add-on
MCP connects context to supported clients, Apex prepares incoming material, and Studio handles focused document and journal creation.
04
Keep everything connected
The output returns to the same OrbitFS environment, so the next workflow can use the updated information instead of starting from scratch.
System design
OrbitFS is built around continuity, not isolated tools.
Files, profiles, permissions and workspace configuration remain the durable layer. Components can be installed, configured, tested, attached, detached, repaired, upgraded or removed around that foundation.
Add capability without rebuilding Base.
New components extend the environment while the core system remains understandable and stable.
Use the right information in the right workspace.
Projects can load their own core files, profiles and references without forcing unrelated material into the workflow.
System and workspace access stay distinct.
OrbitFS can keep global system authority separate from project-level ownership and editing permissions.
Product News and Updates
Latest OrbitFS product updates.
No published product updates yet
Published OrbitFS product news will appear here automatically.
Quick answers
What each part of OrbitFS is responsible for.
Base holds the durable project environment. Add-ons handle specialised jobs while staying connected to that same information.
What is OrbitFS Base?
Base is the main OrbitFS system: files, profiles, workspaces, project structure, permissions and system management. It is the foundation the add-ons work around.
What does a workspace do?
A workspace defines the project-specific working context: what should load first, what is relevant only when needed, which profiles and files matter, and how that material should be treated.
What does OrbitFS MCP do?
MCP connects approved OrbitFS context, startup behaviour, projects, commands and supported clients so the information already organised in OrbitFS can be used directly in connected workflows.
What does OrbitFS Apex do?
Apex is the sorter and converter. It prepares incoming material by classifying, converting and structuring it before the rest of the OrbitFS workflow uses it.
What does OrbitFS Studio do?
Studio is the document and journal-focused creation layer. It works from OrbitFS context and produces content that remains connected to the wider system.
OrbitFS
One foundation. The right tools around it.
Keep your project information organised in Base and extend the workflow with the components you actually need.