I'd define a monorepo as multiple loosely (or un-) coupled projects in the same repository.
The Linux kernel is a single strongly coupled project.
Nevertheless, whether or not you should keep your code in a single repository is more a question of the sheer size of the repository than of whether the code logically belongs in the same place.
But yeah, even the total code of all projects combined at a startup isn't likely to get anywhere close to the scale of the Linux repo, so it's at least a good example of how far you can get with a single large git repo (regardless of the relatedness of the contents therein).
The entire Windows codebase is also a monorepo. It just happens to be a bigger one.