Skip to content
UFFeSciencePublic

About

AkôFlow is an open-source engine for orchestrating and executing container-based scientific workflows in the computing continuum. It was originally developed within the e-Science Research Group at the Institute of Computing, Fluminense Federal University (UFF).

Topics

Resources

Stars

64 stars

Watchers

6 watching

Forks

Repository files navigation

AkôFlow Desktop: scientific workflows across cloud, HPC, and on-premises environments

AkôFlow

Run scientific workflows anywhere.

Latest Desktop release AkôFlow documentation Documentation checks Backend test coverage


Download AkôFlow Desktop   Open the getting started guide

AkôFlow helps you create workflows, choose where they run, execute them, and see the result.

To… Open
Install Desktop Download AkôFlow
Run a SimGrid example First workflow
Explore examples Workflow Showcase
Use the API API reference

Desktop requirements

Use Docker Desktop on macOS and Windows, or Docker Engine with Compose v2 on Linux. Runtime archives are included with each release; no container registry is required.

Academic context

UFFeScience

AkôFlow is developed by the UFFeScience research group at the Institute of Computing, Fluminense Federal University (UFF). The group develops open tools and research for data-intensive science, workflows, and distributed computing.


AkôFlow contributors   Meet the contributors →



AkôFlow contributor avatars

Maintainer release packaging

Create the matching version tag in the Desktop repository before triggering the backend release workflow. Application and runtime builds check out the frozen source tag; packaging fixes can rebuild an existing draft without moving tags:

gh workflow run gh-akf-new-release.yaml \
  --repo UFFeScience/akoflow --ref main \
  --field release_tag=v1.0.10

The optional runtime_artifact_run input can reuse successful runtime archives from a completed tagged-push run only when its repository, tag, source SHA and architecture job all match. Downloaded archives are checked against their SHA-256 manifests before upload. Desktop packages are always rebuilt and their updater metadata verified; a failed publication does not justify reusing an unverified installer.

Windows NSIS and portable executables use distinct setup and portable filenames. Before upload, the Go release-assets-check command verifies updater manifest versions, local filenames, sizes, SHA-512 values and legacy metadata against the actual packages. The workflow creates a draft, not a public release. Review successful checks, runtime checksums, package contents and screenshot provenance before publishing the draft. Do not move an existing source tag to hide a packaging correction.

Cite AkôFlow

If AkôFlow contributes to your research, please cite:

@inproceedings{ferreira2024akoflow,
  author    = {Ferreira, Wesley and Kunstmann, Liliane and Paes, Aline and Bedo, Marcos and de Oliveira, Daniel},
  title     = {AkôFlow: um Middleware para execução de Workflows científicos em múltiplos ambientes conteinerizados},
  booktitle = {Proceedings of the 39th Brazilian Symposium on Databases (SBBD)},
  pages     = {27--39},
  year      = {2024},
  doi       = {10.5753/sbbd.2024.241126}
}

Read the publication.

About

AkôFlow is an open-source engine for orchestrating and executing container-based scientific workflows in the computing continuum. It was originally developed within the e-Science Research Group at the Institute of Computing, Fluminense Federal University (UFF).

Topics

Resources

Stars

64 stars

Watchers

6 watching

Forks

Releases

Packages

Used by

Contributors

Languages