Use Case · Analytics

Scheduled reports on the Software Lifecycle Cloud

Scheduled reports on KERNSTACK are workflows with calendars: a cron trigger starts a worker that computes the period’s numbers from the project’s own tables, renders the report into a bucket file, and delivers it to the recipients — while the run itself is recorded, so a report that did not happen is visible on the day, not discovered in the quarterly review.

Container WorkersApproval WorkflowsObject BucketsProduct Analytics
Talk to us Read Technical Documentation → Software Lifecycle Cloud →

The engineering bottleneck with assembled stacks

Operators paste weekly numbers into a slide because the numbers live in systems that do not publish: someone exports, someone pivots, someone screenshots. The ritual eats a morning weekly, the numbers are irreproducible a month later (“which query made this?”), and the one week the ritual is skipped, a real problem hides inside the gap for a quarter.

Architecture on the Software Lifecycle Cloud

The report is code plus a schedule. The worker reads the same tables the product writes — no export step to drift — computes the defined metrics, and stores both the rendered file and the underlying numbers as a run record keyed by period. Delivery steps send the file link to the bound conversation or inbox. Definitions are reviewed code, so a metric’s meaning has a git history instead of a folklore.

Reproducibility beats polish

A report that can be recomputed for any past period answers the only follow-up that matters — “was it like this last month too?” — with a rerun instead of a shrug. Storing the numbers beside the rendering means next quarter’s comparison does not depend on this quarter’s slide surviving in somebody’s drive.

  • Missed runs are visible: the schedule’s history is run records, or their pointed absence
  • Metric definitions are reviewed code; “revenue” has exactly the meaning of the current definition file
  • Recipients get a bucket link with an expiry — no report PDFs accumulating in inboxes as the record

Delivery people will actually read

The report lands where its audience lives: the project conversation (mirrored to Telegram or WhatsApp where bound), or email through the notify pattern. A three-line summary in chat with the full file behind a link outperforms a beautiful PDF attached to a thread nobody opens.

FAQ

Frequently asked questions

The run record shows the failure and its error, and the workflow can notify the bound conversation the same morning. A silent week is impossible by construction — absence of a success record is itself the alarm.

Yes. The worker takes a period parameter; the computation reads the same tables and the definition version you choose. The regenerated numbers store beside the originals, so definitional changes never rewrite history silently.

Whoever can change the project, through the same review as any code change. The definition’s git history is the audit trail executives actually want when two reports disagree.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Category PillarThe Software Lifecycle CloudWhy people and agents build, deploy, and operate on a single vertically integrated stack.Service · ComputeWorkersContainer workers for long jobsService · OrchestrationWorkflowsDurable workflows with human pausesService · DataBucketsObject storage with presigned uploadService · InsightAnalyticsProduct analytics on the same fabricIndustry SolutionLogistics Cloud SolutionsLogistics products on KERNSTACK give every shipment one timeline and every exception an owner: carrier scans and status callbacks are stored raw, normalised into canonical states per shipment, reconciled against orders by workers, and surfaced — to dispatchers as an exception queue, to customers as a tracking page reading the very same rows. The fog between “the carrier says” and “our system says” is where this architecture earns its keep.Use Case · ProductExperiment assignmentAssignment is a pure function of the subject key and the experiment’s salt — stable across requests, no coordination needed. The function records the assignment row once and serves the variant; outcome handlers were already writing events, which now simply carry the experiment id the assignment returned. Analysis reads assignments and outcomes from neighbouring tables with the same keys.Use Case · AgenciesAgency client deliveryThe studio’s delivery shape is a template stack.json: gateway, functions or workers in the client’s stack languages, tables, buckets, and apps under one target per client, on European infrastructure the studio can name in the pitch. Previews run the same declaration; the client’s approval happens in the bound conversation with a live link. Every client’s meter is separate by construction — the studio sees delivery cost per client without allocation spreadsheets.

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →