# TIBCOSoftware/flogo

Project Flogo is an open source ecosystem of opinionated  event-driven capabilities to simplify building efficient & modern serverless functions, microservices & edge apps.

Repository: https://github.com/TIBCOSoftware/flogo
Canonical: https://ross.abutalabs.com/products/flogo
Homepage: http://flogo.io
Language: CSS
License: BSD-3-Clause
License Family: permissive
Topics: flogo, iot, integration, golang, edge, microservices, serverless, lambda, aws-lambda, tensorflow, faas, functions-as-a-service, kafka-client, kafka-producer, mqtt-client, mqtt-producer, go, faas-framework, rules, streaming
Last push: 2024-04-24T18:42:04+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3706, "days_push": 861, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2492, forks 290 (observed 2026-08-28T04:06:56.502712+00:00)

## What it is
Project Flogo is an ultra-light, Go-based open source ecosystem for building event-driven applications using triggers and actions. It supports application integration flows, stream processing, a rules engine, and native TensorFlow inferencing, deployable as serverless functions, containers, or static binaries on edge devices.

## Use cases
- build lightweight serverless functions in Go
- process IoT edge events with sub-10MB binaries
- run stream processing pipelines on Kafka or MQTT events
- integrate APIs, databases, and apps with event-driven flows
- run TensorFlow model inferencing at the edge
- deploy event-driven microservices as containers or static binaries
- implement business rules that react to incoming events

## When to choose
- you need ultra-lightweight event-driven apps for edge or serverless deployment
- you want a Go-based alternative to heavier Java/Node integration engines
- you need to combine integration flows, streaming, rules, and ML inferencing in one binary
- you consume events from MQTT, Kafka, or other triggers

## When to avoid
- you need a general-purpose web framework with rich HTTP routing
- you prefer a large ecosystem of third-party libraries over a contribution model
- you need heavy GUI-based enterprise integration tooling beyond Flogo's web designer
- your team is not comfortable with Go

## Facets
- artifact type: framework
- maturity: maintenance
- function: microservices, streaming, workflow-automation, machine-learning, serverless, iot, message-queue, webhook
- domain: iot, microservices, developer-tools, machine-learning
- platform: go, cross-platform, cloud, self-hosted, embedded
- tags: event-driven, faas, triggers-and-actions, integration-flows, stream-processing, rules-engine, tensorflow-inferencing, edge-computing, kafka, mqtt, aws-lambda, automation, data-engineering, docker

## Member repositories
- TIBCOSoftware/flogo (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:56.502712+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:27:45.206258+00:00, confidence not recorded.
  - readme: https://github.com/TIBCOSoftware/flogo (fetched 2026-08-28T04:06:56.502712+00:00, sha 5112b16a29ef)
  - homepage: http://flogo.io (fetched 2026-08-29T10:09:32.062413+00:00, sha bb8c5debd3c1)
- Data as of 2026-08-30T08:39:29.467469+00:00.