Want to see what is actually happening behind the screen?
You never need to understand this to use Arythos. This is the optional deep end: a live server check plus realistic examples of the code, database and requests that can power a custom business system.
$ GET /api/lab/server
connecting to the server that rendered this page...
$ watch business_event --type job.completed
›
This page is talking to its own backend.
The panel on the left makes a real request back to the Arythos Flask server. The server checks its database and returns a safe runtime snapshot. Nothing sensitive is exposed.
Follow one action through the whole system.
Imagine an employee clicks Job Complete. Here is how that simple button can travel from the screen to the server, change the database and trigger the next actions.
@app.post("/jobs/<int:job_id>/complete")
@login_required
def complete_job(job_id):
job = jobs.get(job_id)
permissions.require("complete_job", job)
# Save the business change
job.status = "Completed"
job.completed_at = utc_now()
database.save(job)
# Tell the rest of the system what happened
events.emit("job.completed", job_id=job.id)
return {"success": True}What this code means
The route waits for a “complete this job” request. It checks the employee’s permission, changes the job to Completed, saves it, then announces a job.completed event so other pieces can react.
The database is the memory
The pretty dashboard is not the source of truth. The server writes structured records like this so the job is still Completed tomorrow, after a restart, and on another employee’s device.
POST /api/jobs/1048/complete
Content-Type: application/json
Authorization: Bearer ••••••••
{
"completed_by": 7,
"send_customer_update": true
}{
"success": true,
"job_id": 1048,
"status": "Completed",
"automation_started": true
}An API is just a structured conversation
The app says, “complete job 1048.” The server answers, “done.” This same idea lets a website, iPhone app and employee dashboard all talk to the same business system.
@events.on("job.completed")
def after_job_completed(job):
inventory.record_usage(job.materials)
finance.record_revenue(job.total)
customer = customers.get(job.customer_id)
sms.send(
customer.phone,
f"Your {job.vehicle} is ready."
)
reports.refresh("daily_sales")Press run to follow the event.
No fake “hacker screen” claims.
The runtime snapshot on this page comes from the actual server. The business code and customer data shown in the deeper examples are intentionally fictional so the Lab can explain architecture without exposing private source code, credentials or customer information.
Server health
API response, database check, uptime and request count from this running process.
Business code
Realistic Flask/Python patterns showing what an Arythos workflow might look like.
Business records
Fictional job and customer data used only to explain how database state changes.
You do not need to understand any of that
to know what you want fixed.
Tell Arythos the business problem. We can take it from there.
Tell us what is slowing you down ↗