A branded workstation opens into the right surfaces instead of making the user assemble the machine by hand.
Public product preview
The governed AI workstation OS for people who need the machine to think in systems.
TAHAI OS—SENTINEL is a Linux-based workstation platform for governed AI execution, serious development, distributed agents, and visible operator control. It is not a themed desktop, not a chat wrapper, and not a folder of shortcuts. It is the machine-level environment where AI work can be launched, routed, watched, constrained, recovered, and improved. The initial public release is not yet available; the expected public release window is mid–late May 2026.
OSWorkstation platform
NodeLocal contract authority
SENTINELOperator shell
BYOKUser-owned provider access
governed execution fabric
S
TAHAI OS—SENTINEL
Operator workstation
plan
route
execute
verify
recover
Browserresearch + provider consoles
VaultBYOK grants + workspace scope
Workerslocal + LAN execution
Telemetryvisible proof and recovery
01Coming soon
Initial public release is not available yet. Expected public release window: mid–late May 2026.
02Contracts before chaos
OS, Prefrontal Node, SENTINEL, providers, and workers are separated by stable public roles.
03Keys stay user-owned
BYOK is the default posture: provider access belongs to the user, not the platform.
04Execution becomes visible
Routes, jobs, worker state, verification, diagnostics, and recovery are meant to be seen.
Command horizon
From boot to execution, the workstation has a chain of command.
TAHAI OS—SENTINEL is designed so the work does not disappear into a chat box. The machine opens with a curated environment, credentials stay user-owned, Prefrontal Node provides local authority, SENTINEL gives the operator a control surface, and distributed agents report back through visible proof loops.
Provider consoles, documentation, developer resources, and TAHAI ecosystem doors are organized as a working surface.
BYOK provider access is treated as a user-owned capability with clear workspace boundaries.
Prefrontal Node anchors policy, job state, contracts, traces, diagnostics, and recovery expectations close to the machine.
The premium control plane turns coding and distributed-agent work into visible, governed execution.
Routes, workers, approvals, failures, and evidence become part of the operating rhythm instead of hidden side effects.
Control loop
Every serious task needs a visible path from intent to proof.
The workstation story is strongest when the flow is obvious: the operator starts the work, the local authority scopes the route, SENTINEL makes the execution visible, workers do the heavy lift, and the system leaves behind enough signal to verify, recover, or improve the next run.
Start from a clear operator command, workspace, or work mode.
Apply provider grants, local policy, routes, and boundaries before execution.
Move the task through local tools, models, and workers with visible state.
Surface checkpoints, diagnostics, outputs, failures, and recovery signals.
Carry forward what worked without turning the machine into a mystery box.
In plain English
The OS is the control room. SENTINEL is the operator console. Prefrontal Node is the executive core.
The public story is intentionally simple: TAHAI OS—SENTINEL gives AI work a place to live at the workstation level. The browser opens the right doors. The OS organizes the machine. Prefrontal Node gives execution a local authority. SENTINEL turns advanced coding and distributed agents into visible, governed work.
Built around development, provider access, local orchestration, distributed workers, and operator-grade visibility.
Serious work needs routing, keys, tools, storage, jobs, logs, recovery, and policy in one coherent environment.
The platform is designed so execution can be launched, watched, constrained, verified, and recovered.
What the OS is
A workstation operating system shaped around AI work from the first boot screen forward.
The platform brings the pieces that technical operators already use into one governed environment: the desktop, the browser, the developer stack, provider access, orchestration, storage policy, diagnostics, and launch surfaces. The result is an OS that makes complex AI work feel controlled instead of improvised.
Workstation platform
A polished Linux workstation layer for builders who need coding, research, automation, and operator control in one place.
Local-first authority
Prefrontal Node anchors routing, policy, traces, execution contracts, and recovery close to the machine.
BYOK provider control
The platform is designed around user-owned provider credentials, workspace-scoped grants, and visible capability boundaries.
Distributed work
Local and LAN workers become part of the execution fabric instead of hidden background machinery.
Day-one experience
The first session feels like the machine already understands the work ahead.
Boot into a beautiful workstation, open a curated browser, connect provider access, choose the work surface, and route serious tasks through a visible control plane instead of improvising across scattered tabs and scripts.
Branded workstation
Start in a coherent TAHAI OS—SENTINEL environment instead of a generic desktop with AI bolted on later.
Curated browser layer
Provider consoles, documentation, developer resources, and launch surfaces are organized for immediate use.
BYOK access
Connect user-owned provider credentials through scoped grants and capability boundaries.
Prefrontal Node
Use the local orchestration authority for policy, jobs, traces, routing, diagnostics, and recovery expectations.
SENTINEL operator shell
Move into advanced coding, monitoring, distributed-agent control, and verified execution surfaces.
How it is built
Three roles. Frozen contracts. No identity drift.
The platform is intentionally separated so the ecosystem stays understandable as it grows. TAHAI OS—SENTINEL is the workstation platform. Prefrontal Node is the canonical local orchestration daemon and contract authority. SENTINEL is the advanced operator shell that consumes those contracts.
That separation is the difference between a tool pile and an operating environment. Each layer has a job. Each boundary has a purpose. The OS can ship platform surfaces while the coding control plane continues to mature, because the contracts define how the pieces meet.
Layer 01
TAHAI OS—SENTINEL
image, installer, browser, storage, dev stacks, vault UX, policy, update posture
Layer 02
Prefrontal Node
provider routing, jobs, contracts, traces, validation, policy, local execution authority
Layer 03
SENTINEL
operator shell, distributed-agent visibility, monitoring, approvals, verification, recovery
frozen endpoints
stable events
workspace manifests
provider registry
Workstation blueprint
The OS is not one feature. It is the place where the features become one working environment.
The public promise is simple: boot the workstation, open the right surfaces, connect the user-owned providers, choose the work lane, and make execution observable. The blueprint keeps every layer legible so the product can grow without turning into a mystery box.
Branded Linux workstation, tuned for builder workflows and OS-level control.
Research, provider consoles, documentation, launch surfaces, and ecosystem links.
BYOK access, scoped grants, capability boundaries, and workspace-level control.
Curated packs for serious coding, scripting, cloud work, local tools, and AI runners.
Prefrontal Node anchors routes, jobs, traces, events, policies, and recovery signals.
SENTINEL turns distributed execution into visible work the operator can govern.
Build philosophy
The technical posture is visible before the installer is public.
TAHAI OS—SENTINEL is presented as a workstation platform because the product philosophy is larger than a single application. The preview centers five ideas that define the product direction: local authority, user-owned provider access, visible work, bounded execution, and recoverable failure. Those principles are the line between an AI toy and a serious operating environment.
The machine keeps orchestration, policy posture, traces, diagnostics, and recovery expectations close to the workstation.
BYOK keeps AI-provider relationships in the user's hands while the workstation organizes grants, capabilities, and routes.
Jobs, worker state, approvals, checkpoints, provider posture, and support evidence surface instead of hiding behind prompts.
Serious AI work needs scope, contracts, role separation, and policy surfaces before it can be trusted as part of a real workflow.
Recovery, diagnostics, support bundles, and operator-readable evidence are part of the product direction, not afterthoughts.
Before release
How to evaluate the platform before the public release opens.
Until the initial public release is available, the right evaluation is not installation. It is understanding whether the platform's posture matches the way serious AI and development work runs best: governed, observable, user-owned, and ready to mature into team and enterprise control.
Ask 01Do I need AI work to live inside a workstation environment instead of scattered browser tabs?
Ask 02Do I care about visible routing, worker state, diagnostics, and recovery evidence?
Ask 03Do I want provider access to remain BYOK instead of hidden inside someone else's platform account?
Ask 04Would my team benefit from repeatable workstation posture, policy profiles, and supportable operating lanes?
What it does
It turns a machine into a governed AI execution station.
The value is not one more app. The value is that the environment itself begins to support disciplined AI work: onboarding, provider access, stack selection, workspace creation, execution routing, monitoring, troubleshooting, and repeatable recovery.
Launch a serious dev workspace
Open a machine that already understands coding stacks, AI tools, browser research, provider consoles, and workspace structure.
Bring your own providers
Keep provider relationships user-owned while the platform gives keys, capabilities, and grants a cleaner place to live.
Route work through an executive core
Plan, execute, observe, and recover work through a local authority instead of scattering tasks across disconnected tools.
See the system working
Expose job state, provider posture, worker activity, and verification signals where an operator can actually act on them.
Coordinate distributed agents
Connect local and LAN resources into a governed fabric that can expand beyond a single foreground session.
Prepare for team and enterprise use
Build toward policy profiles, support bundles, diagnostics, edition channels, and organization-grade control from the beginning.
Distributed agents
The agent fabric stays visible. The operator never has to guess what is happening.
SENTINEL’s visual language is not decoration. It exists because distributed execution needs visible routing, visible state, visible failures, and visible recovery. The platform is designed to make the work legible.
Operator
OS
Prefrontal Node
SENTINEL
Worker A
Worker B
Local tools
AI provider
Model route
Systems cockpit
A public surface that feels like the product: alive, governed, and under command.
TAHAI OS—SENTINEL is presented as an operating environment because the product itself is meant to bring scattered AI work into one accountable cockpit: credentials, routes, workspaces, agents, diagnostics, recovery, and the operator’s next decision.
Model access stays explicit, scoped, and visible.
BYOK credentials are treated as user-owned access, not platform inventory.
Distributed work is surfaced as state the operator can understand.
Serious execution leaves behind evidence, not guesswork.
Operator proof
The visuals create desire. The operating model earns trust.
TAHAI OS—SENTINEL is framed around evidence surfaces: clear product boundaries, visible job state, bounded provider access, supportable diagnostics, and an execution model that can be explained without hand-waving.
BoundaryOS ≠ Node ≠ SENTINELEach layer has a public responsibility.
AccessBYOK by defaultProvider keys remain user-owned and scoped.
ExecutionJobs, routes, workersWork stays observable, not mysterious.
RecoveryDiagnostics and rollbackFailure states produce useful evidence.
GrowthBrowser → OS → TeamThe product ladder is intentional.
EnterprisePolicy-aware postureBuilt toward channels, support, and admin control.
Trust rails
The public promise is simple: keep power visible, bounded, and recoverable.
The visual impact only matters if the platform feels serious after the first impression. TAHAI OS—SENTINEL presents AI work as a governed operating rhythm: credentials stay scoped, routes stay explainable, workers stay observable, and failure leaves behind usable evidence.
BYOK access is framed around user ownership, workspace grants, and visible capability boundaries.
Provider choice, local authority, job state, and worker activity belong in surfaces an operator can understand.
Diagnostics, checkpoints, support bundles, and rollback posture are part of the platform story, not cleanup afterthoughts.
The OS, browser, Prefrontal Node, and SENTINEL each keep a clear public job so the product ladder stays legible.
Why it is special
This is built to feel like an instrument, not a bundle.
Most AI workflows still live in tabs, prompts, scripts, partial dashboards, and invisible background state. TAHAI OS—SENTINEL moves the control surface down into the workstation itself. That is the category shift: the machine becomes the governed environment.
Category-level positioningOS, node, browser, and operator shell are treated as one ecosystem with separate responsibilities.
Visible execution postureRouting, verification, worker state, and failures belong in the operator’s line of sight.
Public product ladderFree browser acquisition, paid OS flagship, premium SENTINEL differentiation, team and enterprise expansion.
Built for builders and operatorsBeautiful enough to create desire, technical enough to earn trust.
Operator-grade promise
The system shows its work.
Jobs, routes, workers, grants, provider posture, and recovery signals belong where the operator can see them.
The machine respects limits.
Provider access, workspace scope, and execution pathways are treated as controllable surfaces, not scattered secrets.
Failure leaves evidence.
Diagnostics and support bundles are part of the platform direction so serious work can be understood after the fact.
Category shift
Stop treating AI like a tab. Start treating it like an operating environment.
The difference is not aesthetic alone. It is control placement. Ordinary AI workflows scatter authority across browsers, terminals, scripts, dashboards, and hidden background state. TAHAI OS—SENTINEL pulls that authority into a workstation story a user can understand and an operator can govern.
- Tabs, tokens, scripts, and dashboards scattered across the machine.
- Provider state and execution state are hard to explain after the fact.
- Recovery depends on memory, luck, and manual reconstruction.
- The desktop has no opinion about governed AI work.
- OS, browser, vault, node, and operator shell are framed as one environment.
- Routes, workers, provider posture, jobs, and verification become visible surfaces.
- Diagnostics, scoped grants, support bundles, and rollback posture are planned from the start.
- The workstation itself becomes the governed AI execution layer.
Work modes
Different jobs. Same governed workstation.
The OS story is intentionally broader than one coding demo. The platform is meant to support the real rhythm of technical work: research, build, verify, document, recover, and scale the work across machines when a single foreground session is not enough.
Use the browser lane as a curated surface for provider consoles, documentation, project references, and TAHAI ecosystem links.
Use the workstation layer for coding stacks, shell tools, editors, cloud consoles, local services, and project launch surfaces.
Route work through local contracts, scoped provider grants, visible jobs, operator decisions, and recoverable traces.
Bring local and LAN workers into a controlled fabric where distributed agents can be observed instead of merely hoped for.
Provider posturehealthy / degraded / quarantined
Queue depthvisible work state
Worker fabriclocal + LAN nodes
Proof trailplan / patch / verify
route selected through policy
workspace grant scoped
job checkpoint recorded
operator review surface updated
The coding application
SENTINEL is the premium control plane for coding and agentic execution.
SENTINEL is where the advanced work becomes visible: planning, routing, provider health, worker status, job history, approvals, recovery, and verification. It is the operator shell for people who do not want AI coding to behave like a black box.
Visit sentinel.tahai.net →Browser lane
The free browser is the public front door. The OS is the flagship destination.
The standalone TAHAI Web Services Browser introduces the ecosystem through a familiar surface: curated AI and developer bookmarks, provider-console pathways, technical research, and fast onboarding. Inside the OS, the packaged TAHAI—SENTINEL Browser becomes part of the broader workstation experience.
AI provider consoles
Developer references
Workspace launchers
TAHAI ecosystem links
BYOK onboarding paths
Public release pathway
The product is being introduced before the public release so people understand what is coming.
The initial public release is not available yet. The expected release window is mid–late May 2026. Until then, os.tahai.net explains the platform, clarifies the ecosystem, previews the edition ladder, and sets expectations for a workstation OS built around governed AI execution.
Make the OS, browser, node, SENTINEL, editions, and ecosystem roles instantly legible before release.
The first public release window is targeted for mid–late May 2026. Availability language stays clear until release is live.
Expose planning, routing, verification, support bundles, diagnostics, and distributed-agent proof trails as the platform matures.
Move from individual workstation power into policy, support, private channels, and organization-grade control.
Expected release shape
When the public release opens, the promise is not another app. It is a complete workstation lane.
The first public release is expected mid–late May 2026. Until that release is available, the site keeps the boundary clear while showing the shape of what the product is being built to introduce.
A coherent TAHAI OS—SENTINEL workstation identity across the public product experience.
Provider consoles, AI tools, documentation, and ecosystem links organized for day-one orientation.
User-owned provider access and capability boundaries remain core to the product story.
SENTINEL and Prefrontal Node give advanced execution a visible control and authority model.
Until release opens, os.tahai.net remains a product preview and expectation-setting surface.
Who it is for
Built for people who need the machine to become part of the workflow, not just a place where apps happen to run.
The OS story is strongest for builders, operators, technical founders, agencies, and teams that need AI work to become visible, repeatable, and governed. The platform is designed to make serious work feel less scattered without hiding the control surface from the person responsible for the outcome.
Research, code, automate, document, route, and verify work without living across a pile of tabs.
See providers, workers, queues, failures, grants, and recovery paths instead of trusting a black box.
Move toward repeatable stacks, support bundles, policy profiles, and common workstation expectations.
Evaluate AI workstation workflows with clearer boundaries, update discipline, and product separation.
Monetization
Free adoption at the edge. Paid platform at the center. Availability begins after the public release opens.
The monetization story is part of the architecture, but the initial public release is not available yet. The browser creates awareness. The OS is the flagship paid platform. SENTINEL is the advanced premium differentiator. Team and enterprise editions expand the platform into policy, support, private channels, and organization-grade control after the release path opens.
TAHAI Web Services Browser
Standalone public browser lane for awareness, onboarding, provider-console access, and ecosystem discovery.
Coming soonTAHAI OS—SENTINEL
The paid workstation platform for governed AI execution, dev stacks, browser integration, local orchestration, and visible control.
Expected mid–late May 2026SENTINEL
Advanced coding and operator surfaces for planning, routing, verification, distributed agents, and execution telemetry.
Premium laneTeam / Enterprise
Policy profiles, support bundles, diagnostics, private update lanes, org controls, and commercial account paths.
Expansion lane
Adoption path
Browser awareness → Workstation adoption → SENTINEL depth → Team and enterprise scale
The ladder is deliberately clean, but it is still a coming-soon ladder: the free browser introduces the ecosystem, the paid OS becomes the flagship workstation after release, SENTINEL adds the premium control plane, and team or enterprise lanes bring policy, support, diagnostics, and private-channel expectations into the commercial story.
Enterprise posture
Designed to mature into a supportable platform, not a fragile experiment.
The site stays public-facing, but the product direction is serious: diagnostics, policy profiles, edition channels, update discipline, local authority, support bundles, and clean boundaries between products.
Policy-aware designDesigned around controlled access, grants, and boundaries.
Update disciplineBuilt toward reproducible images, rollback expectations, and channel separation.
Supportable surfacesDiagnostics and evidence paths matter from the start.
Clear product separationOS, node, browser, and SENTINEL stay understandable.
Ecosystem map
One ecosystem. Three public doors. No brand confusion.
os.tahai.net explains the workstation OS. sentinel.tahai.net explains the advanced coding and operator application. tahai.net carries the broader TAHAI Web Services identity and browser lane. The connections are intentional, but each surface has a clear job.
Operating systemos.tahai.net
Operator applicationsentinel.tahai.net
TAHAI Web Servicestahai.net
Software portaltahaiportal.com
Adoption path
From first look to serious workstation adoption, the route stays clean.
The ecosystem is designed to let people enter at the right level. The free browser creates a practical first touch, os.tahai.net explains the flagship workstation platform, SENTINEL shows the premium command surface, and team or enterprise lanes give larger organizations a path toward policy, diagnostics, support, and private-channel expectations.
A free, familiar front door for provider consoles, research, documentation, and ecosystem discovery.
The paid flagship workstation platform where the browser, local tooling, Node authority, and operator surfaces come together.
The premium surface for coding work, distributed agents, traces, approvals, verification, and recovery.
Policy profiles, diagnostics, support evidence, private-channel expectations, and organization-grade control.
Ecosystem links
Questions
What is TAHAI OS—SENTINEL?
A Linux-based workstation platform for governed AI execution, serious development, BYOK provider access, distributed agents, and operator-grade visibility.
What is live right now?
The public website and product preview are live. The OS release itself is not publicly available yet; the initial public release is expected in mid–late May 2026.
Can I download TAHAI OS—SENTINEL now?
No. The initial public release is not yet available. The expected public release window is mid–late May 2026.
Is this just a Linux theme?
No. The visual identity matters, but the platform is more than a theme: OS surfaces, browser lane, dev stacks, local orchestration, contracts, storage posture, and the SENTINEL operator shell.
What makes SENTINEL different?
SENTINEL is focused on visible, governed execution: provider posture, jobs, traces, worker fabric, approvals, verification, and recovery instead of black-box AI coding.
Why does BYOK matter?
BYOK keeps provider relationships and credentials user-owned while the workstation gives access, grants, routing, and capability boundaries a clearer place to live.
How do the three public sites connect?
os.tahai.net explains the operating system, sentinel.tahai.net explains the coding and operator application, and tahai.net anchors the broader TAHAI Web Services brand.
What does governed execution mean here?
It means AI work has visible routes, scoped provider access, worker state, checkpoints, diagnostics, and recovery signals instead of hidden execution spread across tabs and scripts.
What does the trust model emphasize?
The public promise is visible, bounded, recoverable work: scoped credentials, explainable routes, observable workers, diagnostics, support evidence, and clean ecosystem roles.
What is expected in the initial public release?
The first public release is expected to introduce the workstation-platform lane: branded OS experience, curated browser orientation, BYOK posture, local orchestration authority, and an operator-control path. The expected public release window is mid–late May 2026.
Why does the site emphasize visible control?
Because serious AI work needs routes, grants, worker posture, checkpoints, diagnostics, and recovery signals that an operator can understand instead of hidden activity spread across tabs and scripts.
How is the product intended to make money?
The standalone browser is the free acquisition lane, the OS is the paid flagship product after public release, SENTINEL is the advanced premium differentiator, and team or enterprise editions expand into policy, support, diagnostics, and organization-grade control.
Where does the browser fit?
The TAHAI Web Services Browser is the free acquisition lane and a useful standalone doorway. Inside the OS, the packaged browser becomes part of the workstation experience without replacing the OS or SENTINEL brands.
Is os.tahai.net the operating system itself?
No. os.tahai.net is the public home for the product story and release preview. The initial public release is not available yet; the expected window is mid–late May 2026.
How can someone evaluate the project before the public release?
Evaluate the operating posture: local authority, BYOK provider access, visible execution, bounded work, diagnostics, recovery evidence, and clear separation between the OS, SENTINEL, Prefrontal Node, and the browser.
What is the most important thing to understand before release?
TAHAI OS—SENTINEL is intended to be a workstation environment for governed AI execution, not a single app, not a generic Linux theme, and not a download that is available today.
Where can I check the official release status?
Use the public release status page section on this site or the machine-readable release-status.json file. Both continue to state that the initial public release is not available yet until that changes.
Is this website the OS build itself?
No. This website is the public product home and release preview for os.tahai.net. The operating system build, installer, update channels, and production support paths remain separate from the website.
os.tahai.net
The public home and release preview for a workstation OS built around governed AI execution.
os.tahai.net explains the operating system before the initial public release opens. sentinel.tahai.net explains the operator application. tahai.net carries the wider TAHAI Web Services brand. Together they frame one ecosystem with clear roles, strong visual identity, and a release window expected in mid–late May 2026.