Roadmap & Feedback
What works in the Git.eu open beta today, what is coming next, and how to report a bug or share feedback.
Roadmap & Feedback
Git.eu is in open beta. This page shows what works today, what is coming next, and how to report a bug or share feedback.
For dates - guest accounts, organisations, the API and webhooks - see What is coming, and when? in the FAQ.
Roadmap
Legend
| Symbol | Meaning |
|---|---|
| ❌ Out of scope | Not planned - out of scope for this phase |
| ⏳ Planned | Planned - development upcoming |
| 🔜 Later | Partial support planned, full feature in a later phase |
| ⚡ In progress | In progress - actively being developed |
| 🚧 Partial | Done - partial in this phase, complete in a future phase |
| ✅ Available | Done - complete & validated |
| 🗑️ Rejected | Rejected |
Note: the beta is not feature-complete, on purpose - we would rather you test what actually exists than show you screens that do nothing yet. Features marked "❌ Out of scope" belong to the longer roadmap that takes Git.eu from a hosting platform to a full DevSecOps platform.
Phases & Versions
| PoC | MVP | Teamwork | |
|---|---|---|---|
| Version | v1.0.0 | v2.0.0 | v3.0.0 |
| Description | Single-user repository | Git hosting | Project management |
| Offer | - | "Git" | "Pro" |
| Targets | - | Solo developers & small teams | SMEs & IT service companies |
| Capability | PoC | MVP | Teamwork |
|---|---|---|---|
| Identity & Access | |||
| Account | ✅ | ✅ | ✅ |
| MFA basics | ✅ | ✅ | ✅ |
| MFA recovery codes | ✅ | ✅ | ✅ |
| MFA Advanced | ✅ | ✅ | ✅ |
| MFA trusted devices | ❌ | ✅ | ✅ |
| Git CLI OAuth Access | ❌ | ✅ | ✅ |
| GDPR rights | ❌ | ❌ | ⏳ |
| Enterprise SSO | ❌ | ❌ | ❌ |
| Google / GitHub OAuth | 🗑️ | 🗑️ | 🗑️ |
| Code Hosting | |||
| Repository lifecycle | ✅ | ✅ | ✅ |
| Git over HTTPS and SSH | 🚧 | ✅ | ✅ |
| Code browser | ✅ | ✅ | ✅ |
| Local repo import | ❌ | ✅ | ✅ |
| Platform import | ❌ | 🚧 | ⏳ |
| Advanced repo settings | ❌ | 🚧 | ⏳ |
| Repository operations | ❌ | ❌ | ⏳ |
| Reading experience | ❌ | 🚧 | ⏳ |
| Raw file server | ❌ | ❌ | ⏳ |
| Download and upload | ❌ | ❌ | ⏳ |
| Cherry-pick / revert | ❌ | ❌ | ⏳ |
| Code search | ❌ | ❌ | ⏳ |
| Organization import | ❌ | ❌ | ⏳ |
| LFS | ❌ | ✅ | ✅ |
| LFS file locking | ❌ | ❌ | ⏳ |
| Packages | ❌ | ❌ | ❌ |
| File history | ❌ | ❌ | ⏳ |
| Online file editor | ❌ | ❌ | ❌ |
| Collaboration | |||
| Organizations | ❌ | ❌ | ⏳ |
| Collaborator roles | ❌ | ❌ | ⏳ |
| Issues and pull requests | ❌ | ❌ | ⏳ |
| Code review | ❌ | ❌ | ⏳ |
| Project boards | ❌ | ❌ | ⏳ |
| Milestones and roadmaps | ❌ | ❌ | ⚡ |
| Releases | ❌ | ❌ | ⏳ |
| Wiki | ❌ | ❌ | ⏳ |
| Community | |||
| Community space | ❌ | 🚧 | ⏳ |
| Hosted community services | ❌ | ❌ | ⏳ |
| Community connectors | ❌ | ❌ | ❌ |
| Marketplace and partners | ❌ | ❌ | ❌ |
| Automation | |||
| CI/CD connectors | ❌ | ❌ | ❌ |
| Webhooks | ❌ | ❌ | ❌ |
| Native CI/CD engine | ❌ | ❌ | ❌ |
| Secrets and dev environments | ❌ | ❌ | ❌ |
| Feature flags | ❌ | ❌ | ❌ |
| DevSecOps connectors | ❌ | ❌ | ❌ |
| Code scanning | ❌ | ❌ | ❌ |
| Policy enforcement | ❌ | ❌ | ❌ |
| BOM and dashboard | ❌ | ❌ | ❌ |
| Business | |||
| Offer and plans | ❌ | ⚡ | ⏳ |
| Quotas | ❌ | ❌ | ⏳ |
| Payment and invoicing | ❌ | ❌ | ⏳ |
How to help
You do not need to click every button and flag typos. Here is what is actually useful:
- Use Git.eu on a real workflow. A personal project, a realistic repository, anything that reflects how you actually work. Real context surfaces friction that synthetic testing never catches.
- Report friction, not just bugs. "It works but feels off" is valuable feedback. "I expected X, got Y" even more so.
- Give us context. A bug report without context is nearly useless: what happened, in what environment, with which steps, and what impact it had on your workflow.
- Share your ideas - even the long-shot ones. What you want in 6 months or in 3 years: technical, UI/UX, connectors, integrations, marketplace. That input shapes the roadmap even when we cannot act on it right away.
- Be direct. If something is bad, say so.
The friction points reported most often move up in our priorities.
Report a bug or share feedback
Post on r/GitEUBeta and pick a flair:
| Flair | When to use |
|---|---|
🐛 Bug | Unexpected behavior, error, crash |
💡 Idea | Feature suggestion, UX improvement, or ecosystem thought - connectors, integrations, marketplace |
❓ Question | You are stuck and not sure if it is a bug or a beta limitation |
📊 Usage feedback | General observation about your experience, no specific bug |
🗂️ Misc | Anything that does not fit the other categories |
For anything private - your account, your billing, or a security issue - write to support@git.eu instead of posting in public.
Bug report template
**Environment**
OS: [e.g. Ubuntu 24.04 / macOS 15]
Browser: [e.g. Firefox 140]
**What I was trying to do**
[One sentence]
**What happened**
[Precise description - include the error message if any]
**Steps to reproduce**
1.
2.
3.
**Impact on my workflow**
[ ] Blocking [ ] Workaround possible [ ] Minor
You do not need to fill every field every time - but the more context you give, the faster we can act on it.