Open-source projects by TFast Digital Agency

TFast Digital Agency publishes six open-source repositories on GitHub: one original smart-home starter kit for Home Assistant, and five Uganda-focused starting points built on established open-source projects (OpenMRS, ChurchCRM, Gibbon, OSPOS and GrapesJS). Every repository carries its own licence file, and we state clearly which work is ours and which belongs to the upstream projects.

Key facts

  • Publisher: TFast Digital Agency, Uganda. TFast is a business, not a charity or non-profit.
  • Where: github.com/tfastdigital
  • Cost of the code: free to use under each repository's licence (listed below). Setup, hosting, training and support are paid services.
  • Contact: tfastdigital256@gmail.com
  • Last verified against GitHub: 1 October 2026

Which open-source projects does TFast Digital Agency publish?

The table lists every repository we are presenting as open source today. "Built on" names the upstream project whose source code the repository contains. Licence names come from each repository's own LICENSE file.

Project What it does Built on Language Licence Status (from its README)
tfast-home-assistant A ready-to-run starter kit for Home Assistant: a two-view mobile dashboard (Home and Energy), three commented automations (morning routine, away mode, hallway light on motion), a "goodnight" script, light and dark themes and setup guides. Home Assistant (configuration layer; not a fork of Home Assistant) YAML configuration, Markdown docs MIT, © 2026 TFast Digital Agency Version 1.0.0. Original TFast work.
tfast-clinic Planned clinic and hospital records system for Ugandan health centres. OpenMRS Java MPL-2.0 (OpenMRS) Proposed. Contains OpenMRS source plus our planning README.
tfast-church Planned church management with mobile money giving and SMS for Ugandan churches. ChurchCRM PHP MIT (ChurchCRM) Proposed. Contains ChurchCRM source plus our planning README.
tfast-school Planned school management platform with mobile money fee payment for Ugandan schools. Gibbon PHP GPL-3.0 (Gibbon) Proposed. Contains Gibbon source plus our planning README.
tfast-pos Planned retail point of sale for Ugandan shops, with EFRIS and mobile money support intended. Open Source Point of Sale (OSPOS) PHP MIT (OSPOS). The OSPOS footer notice must stay visible. Proposed. Contains OSPOS source plus our planning README.
tfast-site-builder Planned drag-and-drop website builder for small businesses in Uganda. GrapesJS TypeScript BSD-3-Clause (GrapesJS) Proposed. Contains GrapesJS source plus our planning README.

What is original TFast work and what is upstream code?

Only tfast-home-assistant is original TFast work. The other five repositories are snapshots of well-known open-source projects, kept with their original licence files, to which we added a NOTICE file crediting the upstream project and a README describing the Ugandan version we plan to build. As of 1 October 2026 their READMEs are marked "Proposed", and they do not yet include the Uganda-specific features (such as mobile money or EFRIS) that the READMEs describe. Copyright in the upstream code stays with its original authors, and their licence terms apply.

How do I use or contribute to these projects?

  1. Pick a repository from the table and open it on GitHub.
  2. Read its README and LICENSE first. The README explains what the repository contains; the LICENSE tells you what you may do with it.
  3. Try tfast-home-assistant: follow its How to use steps and quick start guide. You need a running Home Assistant installation, version 2024.2 or newer.
  4. Report a problem or suggest an improvement by opening an issue on the repository's Issues tab. For tfast-home-assistant, read CONTRIBUTING.md first: open an issue for anything bigger than a small fix, then send a pull request.
  5. For the upstream-based repositories, bugs in the original software are best reported to the upstream project (OpenMRS, ChurchCRM, Gibbon, OSPOS or GrapesJS). Use our issues for anything specific to the Ugandan version.

Frequently asked questions

Are these projects free?

The source code is free to use under the licence shown for each repository (MIT, MPL-2.0, GPL-3.0 or BSD-3-Clause). Read the licence before you redistribute or build on it, because GPL-3.0 and MPL-2.0 carry conditions that MIT does not. TFast Digital Agency is a business, so installation, hosting, training and support are paid services; the code itself is not sold.

Can I contribute?

Yes. Open an issue or a pull request on the repository concerned. tfast-home-assistant has a CONTRIBUTING.md that asks for small, readable, commented changes. For the upstream-based repositories, changes to the original software belong with the upstream project.

Who maintains these repositories?

TFast Digital Agency, Uganda, publishes them from the GitHub account tfastdigital. The tfast-home-assistant README describes it as built and maintained by TFast Digital Agency. The upstream projects are maintained by their own communities.

Are the Ugandan features (mobile money, EFRIS, NSSF) already built?

Not in the public repositories. As of 1 October 2026 the READMEs of the five upstream-based repositories describe them as proposed, and our check of the files found no mobile money, EFRIS or NSSF code in them; they contain the upstream source code. If you need a working setup, see our services or contact us.

Is TFast Digital Agency a charity or non-profit?

No. TFast Digital Agency is a business. Publishing these repositories is part of how we work in the open; it is not a charitable programme.

Where are TFast's other tools?

This page covers only the repositories we present as open source. It does not describe TFast's commercial tools or services; see our services for those.

Need help using or adapting one of these projects?

We can install, host, adapt and support open-source software for businesses in Uganda. See our services, write to tfastdigital256@gmail.com, or use the contact page. You can also browse everything we publish at github.com/tfastdigital.

Last updated: 1 October 2026. Sources: each repository's README, LICENSE and NOTICE files on GitHub, read on 1 October 2026. Project and trademark names belong to their respective owners.

We use cookies to keep the site working and to understand how it is used. learn more

Allow