Run code without losing the trail.
Use named inputs, logs and outputs for manual or scheduled jobs.
Move existing code into a repeatable run.
Give the code you already have a defined place to run and a record of what it did.
Bring the code
Use Python and the Novem CLI with supported repositories, files and outputs. Existing scripts stay recognisable.
Name what it needs
Define the inputs, credentials and outputs so the run does not depend on someone's local file path.
Run and inspect it
Each execution produces logs and a record of what ran, what it read and what it produced, whether it started manually or on a schedule.
From script to scheduled job.
Named inputs, one run and finished outputs.
novem -j daily_report -R @data.csv @config.jsonnovem -j daily_report -r logecho "0 8 * * *" | novem -j daily_report -w config/scheduleThe team can run it again without the original laptop.
What a production run needs.
Before a pilot, the team should know where the code runs, what it can reach and how to inspect the result.
A defined environment
Jobs run in an environment managed by Novem so their behaviour does not depend on an analyst's machine.
Named access
Give the job the sources and credentials it needs for the task.
A run record
Keep the logs with the run and the outputs it produced.
One job definition
Use the same job definition for manual and scheduled runs.