Fossify Keyboard is a text insertion keyboard that asks for no internet

A keyboard whose main job is inserting text you already wrote

The project description is a one liner and it sets the scope: an easy keyboard for inserting all kinds of texts, special characters and numbers. That is the whole idea, and it is narrower than it first appears. Fossify Keyboard is not presented as a general purpose typing keyboard with clever prediction, and the feature list does not mention dictionaries, autocorrect, swipe input or suggestions. What it lists instead is a clip board, offline operation, multiple languages and layouts, customisable colours and a set of toggles. So the audience is the person whose typing is dominated by repetition: the developer pasting a connection string, the support agent pasting a canned reply, the person typing the same postal address in five forms. The interesting part is that such a tool can replace the keyboard entirely, which is a bolder claim than adding a clipboard manager to an existing keyboard, and it changes the threat model of what you type, because a keyboard is the one app that sees everything you enter in every other app.

No internet permission is the feature that defines the app

The README leads with the offline claim and explains why it matters in terms of privacy, security and stability rather than in terms of features. Fossify Keyboard operates entirely offline without internet permission, allowing you to use it anytime, anywhere, without needing an internet connection, and this is presented as providing more privacy, security and stability compared to other keyboards that connect to the internet. That is the correct framing, and it is the one part of the README worth reading closely. A keyboard that requests no network access cannot exfiltrate what you type, and because the app does not need the permission, the operating system can enforce that. The privacy statement that follows is consistent with it: the app does not collect or share any user information with third parties, so your typing activity stays private. The open-source transparency claim completes the argument, since the point of an auditable keyboard is that you can check the claim rather than trust a privacy policy. For a person who types passwords, one time codes and medical or legal details into other apps, a keyboard with no network permission removes an entire category of risk, and for a fleet or a family device it removes the question of what a preinstalled keyboard might be doing.

Clips, pinned items, and the settings that change how it feels

The feature list is short and each entry is concrete. The handy clip board is the core: you create clips and pin frequently used ones for easy access, which allows you to insert your most used texts quickly, saving time and effort. The pinning is the detail that makes it usable, since a clip board without pinned items is a list you have to scroll. The customisable settings are named as toggles rather than as a list of sliders, covering vibration, popups on key press and the selection of the preferred language from the list of supported ones. The design and dark theme entry says the app ships with a default dark theme, and the customisable colours feature says you can choose and adjust colours to match your style. The multiple languages and layouts entry says you can choose from a wide variety of languages and keyboard layouts, which makes it easy to switch and type in your preferred language. Taken together, the picture is a keyboard that is mostly a text insertion surface with a store of your own strings, and the customisation is about feel, vibration and popups, which is the part users notice most in daily use.

Getting it, and what the repository actually contains

There are no build or install instructions in the README, so the project says to get it from the usual Android distribution channels, and the badges at the top of the file point at Google Play, F-Droid and IzzyOnDroid. The IzzyOnDroid link in particular matters for the audience, because a F-Droid or IzzyOnDroid install is the normal route for someone who does not want a proprietary store account on a device that is meant to be private. The repository itself is a conventional Android project written in Kotlin. The top level listing shows an app/ directory for the application module, build.gradle.kts and settings.gradle.kts for the Gradle build, gradle.properties, a gradlew wrapper with its Windows counterpart, a gradle/ directory, and a .fossify/ directory. The build tooling is modern and Kotlin-first, and the fastlane/ directory holds the store metadata, including the phone screenshots the README embeds under fastlane/metadata/android/en-US/images/phoneScreenshots/. There is a detekt.yml and a lint.xml for static analysis, a .editorconfig, a CODEOWNERS file, a CHANGELOG.md, a CONTRIBUTING.md and a Gemfile with a Gemfile.lock, which points to the Ruby tooling around the release process. Two files are worth naming as a caution. keystore.properties_sample sits at the root, which is the template for the release signing configuration, and crash.log is checked in, which is either a leftover or a deliberate sample.

The tradeoffs of replacing your keyboard entirely

The obvious comparison is with any general purpose Android keyboard, and the difference in approach is not in the typing but in the network model. A mainstream keyboard sends what you type to a cloud service for autocorrect, suggestions, translation and voice input, and that is what makes it capable and also what makes it a privacy question. Fossify Keyboard takes the opposite position: no permission, no service, no data leaving the device, which means the convenience features that require a server are simply absent rather than merely optional. The cost is that you are giving up the things a network provides, and the README's own feature list is the evidence. There is no mention of a learning dictionary, of swipe or gesture input, of multilingual word prediction, of voice dictation, of emoji prediction, of a translator, or of the cross-device sync that cloud keyboards offer. For the person who mostly types in one language, does not want suggestions, and mainly wants to paste a few fixed strings, that is a good trade. For the person who writes long messages, switches languages mid sentence, or relies on voice input, it is not, and the app will feel bare. The second difference is the consequence of the first. Once this is your only keyboard, every character you type on the device goes through it, so a bug or an unwanted data path in a keyboard app is a much larger exposure than in a utility you open occasionally.

Licence, maintenance and where the project fits in the Fossify family

The licence is GPL-3.0, which is the licence to read carefully if you intend to fork the app rather than just use it, since a derivative distribution carries the copyleft obligations, and the repository ships a LICENSE file for that. The project belongs to the Fossify organisation, whose site is fossify.org and whose GitHub organisation is FossifyOrg, and the README invites you to explore more Fossify apps, to follow the community on Reddit or Telegram, and to read the source code. That family context is the useful part for an evaluator, because a Fossify application is typically one focused utility with a shared look, and the pattern of a small scope, a store listing, an F-Droid build and an open issue tracker is consistent across it. On maintenance, the project is not archived and the last push was on 2026-10-19, so the code is being worked on. The release list on record is 1.9.1 from 2026-02-02, 1.9.0 from 2026-01-30 and 1.8.0 from 2025-12-29, so the tagged versions and the commit activity are not in step, which is normal for a store-published app where the release pipeline and the repository are separate, and it means the version in the store may be ahead of the newest tag you can see. The CHANGELOG.md in the repository is the place to see what changed between the versions you can read about.

Editorial conclusion

Fossify Keyboard suits an Android user who types the same strings repeatedly, addresses, boilerplate replies, codes, and who wants a keyboard that asks for no internet permission and is available as auditable source. It is the wrong tool if you want a full featured typing keyboard, because the feature list is about inserting prepared text rather than about predictive typing, dictionaries or autocorrect, and the wrong tool if you rely on a hardware keyboard, since the app is an input method for the on screen keyboard. Before you switch to it, check the language and layout list against the ones you actually type in, and note that the releases on record are 1.9.1 from 2026-02-02 and 1.9.0 from 2026-01-30 while the repository was pushed on 2026-10-19, so a newer build may exist in the store than in the tag list.

Frequently asked questions

Official sources

1. FossifyOrg/Keyboard on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases