| 1 | <% content_for :title, "About" %> |
| 2 | <% content_for :description, "About siGit — Git hosting for the AI era: repositories, open-weights model hosting, and AI coding agents over the Agent Client Protocol." %> |
| 3 | |
| 4 | <div class="max-w-3xl mx-auto px-4 sm:px-6 py-16 sm:py-20"> |
| 5 | <div class="text-center mb-12"> |
| 6 | <img src="/icon.png" alt="siGit Code & Deploy" class="mx-auto h-20 w-auto rounded-2xl border border-surface-600 shadow-lg"> |
| 7 | </div> |
| 8 | |
| 9 | <div class="prose-readme"> |
| 10 | <h1>siGit Code & Deploy</h1> |
| 11 | |
| 12 | <p> |
| 13 | siGit is Git hosting for the AI era. Version your repositories, publish |
| 14 | open-weights models with full model cards and LFS-backed files, and hand the |
| 15 | keys to your AI agent over the Agent Client Protocol. Code and models live |
| 16 | side by side, in the same storage and the same calm UI. |
| 17 | </p> |
| 18 | |
| 19 | <h2>Why this exists</h2> |
| 20 | <p> |
| 21 | We kept running into the same split. Source code lived in one place, model |
| 22 | weights lived somewhere else, and the two never really met. Pushing a model |
| 23 | meant a different tool, a different account, and weights scattered across |
| 24 | services. |
| 25 | </p> |
| 26 | <p> |
| 27 | So we built siGit. It is plain Git underneath, so nothing about your workflow |
| 28 | has to change, but it treats a multi-gigabyte model the same way it treats a |
| 29 | source file: something you can host, browse, and version without fuss. |
| 30 | </p> |
| 31 | |
| 32 | <h2>What it does</h2> |
| 33 | <ul> |
| 34 | <li>Host public and private repositories with fast diffs and deep file browsing</li> |
| 35 | <li>Clone, fetch, and push over Git with token-authenticated HTTPS</li> |
| 36 | <li>Publish open-weights models with model cards parsed straight from your README</li> |
| 37 | <li>Store large weights with Git LFS, and see sizes, formats, and quants at a glance</li> |
| 38 | <li>Connect AI coding agents over the Agent Client Protocol</li> |
| 39 | <li>Use the JSON API and the siGit Code & Deploy desktop and mobile apps</li> |
| 40 | <li>Deploy through smbCloud</li> |
| 41 | </ul> |
| 42 | |
| 43 | <h2>Who makes it</h2> |
| 44 | <p> |
| 45 | siGit is built by <a href="https://5mb.app" target="_blank" rel="noopener noreferrer">Splitfire AB</a>, |
| 46 | a small software company in Sweden. Authentication, email, and deploys run on |
| 47 | the <a href="https://smbcloud.xyz/" target="_blank" rel="noopener noreferrer">smbCloud</a> |
| 48 | platform. We use siGit ourselves daily, which keeps the bug list honest. |
| 49 | </p> |
| 50 | <p> |
| 51 | Questions or feedback: |
| 52 | <a href="mailto:splitfire@setoelkahfi.se">splitfire@setoelkahfi.se</a>. |
| 53 | </p> |
| 54 | </div> |
| 55 | |
| 56 | <div class="mt-12 border-t border-surface-600 pt-8 text-center"> |
| 57 | <h2 class="text-lg font-semibold text-gray-100 mb-5">Get the app</h2> |
| 58 | <div class="flex flex-wrap items-center justify-center gap-4"> |
| 59 | <a href="https://apps.apple.com/se/app/sigit-git-client-code-editor/id6753018849" target="_blank" rel="noopener noreferrer" aria-label="Download on the App Store"> |
| 60 | <img src="/images/Download_on_the_App_Store_Badge_US-UK_RGB_blk_092917.svg" alt="Download on the App Store" class="h-10"> |
| 61 | </a> |
| 62 | <a href="https://play.google.com/store/apps/details?id=xyz.smbcloud.SiGit" target="_blank" rel="noopener noreferrer" aria-label="Get it on Google Play"> |
| 63 | <img src="/images/GetItOnGooglePlay_Badge_Web_color_English.png" alt="Get it on Google Play" class="h-10"> |
| 64 | </a> |
| 65 | <a href="https://apps.microsoft.com/detail/xp9k321rf5mzsz?ocid=webpdpshare" target="_blank" rel="noopener noreferrer" aria-label="Get it from the Microsoft Store"> |
| 66 | <img src="/images/MicrosoftStore_Badge_Web_dark.svg" alt="Get it from the Microsoft Store" class="h-10"> |
| 67 | </a> |
| 68 | </div> |
| 69 | </div> |
| 70 | </div> |