Files
app/docs/getting-started/index.md
T
stroblmeandClaude Opus 5.5 01495aed25
Docs / docs (push) Successful in 23s
pre-commit / pre-commit (push) Failing after 2m28s
Test Backend / test-backend (3.12) (push) Successful in 4m51s
Test Backend / test-backend (3.14) (push) Successful in 4m49s
Docs: x86 and arm64, Raspberry Pi included; one container in the start pages
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 14:56:08 +02:00

1.3 KiB

Pick your starting point

Choose the setup that fits your work. Both paths lead to the same Fluksio engine, with a first flow to try along the way. This is really just about a decision what you're planning to do with Fluksio.

Data science

"I have some Python code. I want to keep track of what I ran."

Install Fluksio with pip in your research environment. Turn a function into a node, record metrics and artifacts, and compare experiments. Connect to fluksio.com for the browser dashboard.

Start with Python →

Facility automation

"I have a bunch of sensors. I want them to do something."

Start one Docker container for a local engine and browser interface, on a server, a PC or a Raspberry Pi. Build a live flow, connect your devices, and put their values on a dashboard.

Start with Docker →

Next steps