Aster Terminal
SSH, diagnostics, service administration, BIND, and nftables from the shell.
AN ENTERPRISE IT SIMULATION
Run systems, investigate incidents, manage users, troubleshoot networks, and build real IT experience inside a persistent simulated company.
In your browser. Inside your own company.
Aster Browser
desk.nova.cloud · Service Desk
Aster Terminal
OPS-01 · Aster Shell
Aster Workstation OS 8.1 · astsh
operator@acct-01:~$ nc -vz files-01.nova.internal 445
nc: connect to files-01.nova.internal (10.20.20.25) port 445 (tcp) failed: Operation timed out
Your work carries into the next shift.
A Unix-style shell with stateful commands.
Fix the system. Then prove it works.
One connected operating environment.
YOUR COMPANY ACTUALLY EXISTS
Start inside a simulated organization with its own people, departments, infrastructure, and work queue. An employee’s account belongs to a person. Their workstation sits on a network. The application they need runs on a server.
You work through that company’s problems, one verified change at a time.
Nova Systems
SaaS company blueprintAster Browser
directory.nova.internal · Directory
ONE INCIDENT. MULTIPLE SYSTEMS.
Accounting cannot reach shared files. Is it DNS, a route, a firewall rule, or the server? Inspect the affected workstation and follow the evidence. In this incident, the service is healthy and the policy is blocking the connection.
Other families ask you to investigate stopped services, missing directory membership, or application entitlements. Each repair is checked against the underlying company state.
Aster Browser
desk.nova.cloud · Service Desk
Name resolution
$ dig files-01.nova.internal
;; ->>HEADER<<- opcode: QUERY, status: NOERROR ;; ANSWER SECTION: files-01.nova.internal. 60 IN A 10.20.20.25 ;; SERVER: 10.20.20.53#53(dns-01.nova.internal)
FW-01 · nftables
$ nft -a list ruleset
ip saddr 10.20.10.31/32 ip daddr 10.20.20.25/32 tcp dport 445 drop comment "Temporary containment rule blocking Accounting access to FILES-01." # handle 9
ip saddr 10.20.10.0/24 ip daddr 10.20.20.0/24 drop comment "User VLAN cannot otherwise initiate connections to servers." # handle 8FILES-01 · service state
$ systemctl status smbd
● smbd.service - smbd service
Loaded: loaded (/etc/systemd/system/smbd.service; enabled)
Active: active (running)
Listen: 0.0.0.0:445Firewall output is an excerpt. Real work also checks routes, relevant logs, and identity policy when the symptoms require them.
THE WORKSTATION
Use Aster Browser for company applications. Open Aster Terminal for the command line. Connect over SSH to the host that owns the service, inspect its journal, and make the change there.
Familiar tools, modeled against company state
whoamiip addrpingdigsshsystemctljournalctlnftAster Browser
servers.nova.internal · Server Console
Each host has its own system state.
Local users. Installed packages. Network interfaces. Files and services. A command runs on the computer you’re connected to.
operator@files-01:~$
Aster Terminal
OPS-01 · Aster Shell
Aster Workstation OS 8.1 · astsh
operator@ops-01:~$ whoami
operator
operator@ops-01:~$ ip addr
1: lo: <LOOPBACK,UP> mtu 65536
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500
inet 10.20.10.44/24 scope global eth0operator@ops-01:~$ ping 10.20.20.25
PING 10.20.20.25 (10.20.20.25) 56(84) bytes of data. 64 bytes from 10.20.20.25: icmp_seq=1 ttl=63 time=0.42 ms 64 bytes from 10.20.20.25: icmp_seq=2 ttl=63 time=0.39 ms 64 bytes from 10.20.20.25: icmp_seq=3 ttl=63 time=0.41 ms 3 packets transmitted, 3 received, 0% packet loss
operator@ops-01:~$ ssh files-01
Connected to files-01 (10.20.20.25). Aster Server OS 8.1 — files-01 Headless system. Manage local services with systemctl and journalctl.
operator@files-01:~$ systemctl status smbd
● smbd.service - smbd service
Loaded: loaded (/etc/systemd/system/smbd.service; enabled)
Active: active (running)
Listen: 0.0.0.0:445operator@files-01:~$ journalctl -u smbd
smbd[287]: file service initialized smbd[287]: listening on tcp/445
WHAT YOU WILL PRACTICE
Move from the reported symptom to evidence, a safe change, and an observed result. Practice the skills together, in the environment where they belong.
Read the request, identify the affected resource, and take ownership.
Work with host-specific files, packages, and system commands.
Compare addresses, interfaces, routes, and connectivity.
Diagnose name resolution and update records on DNS-01.
Read ordered policy and repair narrowly scoped connectivity.
Trace directory groups through application entitlements.
Connect to the owning server over an approved SSH path.
Inspect the host’s journal for evidence of service state.
Check listeners and restore stopped server services.
Revoke a lost badge and verify that entry is denied.
Inspect accounts and manage their status and membership.
Read inventory, ownership, deployment, and compliance records.
YOUR TOOLS
Company applications live in Aster Browser. Native tools belong to your workstation. They all see the same company state.
DNS and firewall administration use BIND and nftables on their owning hosts. Graphical remote desktop and company messaging are still in development.
SSH, diagnostics, service administration, BIND, and nftables from the shell.
Your queue, requesters, work notes, objectives, and shift progress.
Workforce accounts, security groups, application roles, and effective access.
Company topology, device addresses, network paths, and firewall policy.
Inventory, service status, and the context for remote administration.
Issued credentials, door policies, badge changes, and access decisions.
Device ownership, deployment, compliance, and asset lifecycle records.
The workstation’s filesystem, with files belonging to their own host.
Internal runbooks, network standards, and troubleshooting guidance.
THE COMPANY REMEMBERS
Files you create, service changes, DNS records, firewall rules, directory membership, and application assignments are saved with your company.
End the shift and review what you resolved. The next day brings a fresh seeded queue alongside noncritical carryover, without resetting your infrastructure or completed work.
Systems
Host files, configuration, and service state
People
Directory status, groups, roles, and credentials
Work
Tickets, verified repairs, and shift summaries
Resume a saved company from My Companies. Window positions and browser layout are not yet persisted.
SCENARIO EXAMPLES
Five generated incident families, eight root-cause variants, and a fresh queue each shift. Requests draw from your company’s people and resources.
DNS resolution
Compare the lookup with inventory, correct the A record, and verify access by hostname.
DNS · Workstation · Web server
File connectivity
Reproduce the failure, inspect the firewall, and restore only the required TCP/445 path.
Workstation · Firewall · File server
Service recovery
Inspect the service and its journal, restore it, and retest from the affected client.
SSH · Service state · Logs
Application access
Inspect the account and application policy. Restore group-based access rather than an individual exception.
Directory · IAM · Effective roles
Directory membership
Find the missing approved membership and verify the resulting application role.
Account · Security group · Application
Lost credential
Disable that credential, keep the employee’s account active, and test denial at the reader.
Credential · Person · Door policy
Create your company, enter your workstation, and start investigating your first incident.