# # Help & Support

> Gitaflow is offered completely free and open-source for anyone wishing to self-host the platform. If you have questions along the way, there are many resources, both free and paid, to help you get up-and-running smoothly.

- Troubleshooting Steps
- Support Tiers
- Sponsored Work
- Frequently Asked Questions

## # Troubleshooting Steps

If you're experiencing issues or think you have found a problem in Gitaflow, be sure to follow these steps before Reporting a Bug:

1. Ensure your server and database meet the minimum requirements.
2. Ensure you’re on the latest version
   (opens new window) of Gitaflow.
3. Stop `CTRL+C` and restart the server `npx gitaflow start`.
4. Run the database migration script: `gitaflow database migrate:latest`
   Note: backup your database first.
5. Disable any data-caching within your project.
6. Test any app issues with both browser extensions and caching disabled (i.e. Incognito Mode).
7. Confirm the issue is not related to your own custom code.
8. Check for existing Issues
   (opens new window) (and Discussions
   (opens new window)) that match your problem.

Source Contributors

If you have installed from source, then you should also remove all dependencies by running `npx lerna clean -y` and reinstall them with `npm install`

If you're still experiencing a problem after completing the above steps, you can chat through things on our community support or report a bug.

## # Support Tiers

### # Community Support

GitHub Discussions
(opens new window) is a great first place to reach out for help. Our community and core developers often check this platform and answer posts. It has the added benefit of being an archival resource for others developers with similar questions.

Our Discord Community
(opens new window) is another great way to get assistance. Please keep all questions on the `#help` channel, be considerate, and remember that you are getting free help from the community for a free product.

No Guaranteed Response Time

While the Gitaflow Core Team plays an active and engaged role in community discussions, there is no guaranteed response time for Community Support.

### # Basic and Premium Support

Basic and Premium Support offer direct communication with the Gitaflow Core Team. Basic support is included on all Enterprise Projects, and Premium Support adds 24/7 response times for critical software issues only.

Cloud customers and Self-Hosted users interested in learning more about our monthly retainer agreements should contact us at support@gitaflow.io.

## # Sponsored Work

### # Commissioned Features

If you need a specific feature added to Gitaflow faster than the normal development timeline, reach out to us
(opens new window) for a quote. Our parent agency will often help subsidize the cost of developing new features if they pass our 80/20 Rule and can be merged into the core codebase. Other custom/proprietary development will be built bespoke within our robust extension system.

### # Expedited Fixes

We triage all reported bugs based on priority and how long the fix is estimated to take. If you need a specific issue resolved sooner, reach out to us
(opens new window) for a quote.

## # Frequently Asked Questions

### # Does Gitaflow support Mongo/NoSQL?

Not currently. Gitaflow has been built specifically for wrapping relational databases. While we could force Mongo to use tables, columns, and rows via Mongoose object modeling, that approach of "faking" a relational structure in a non-structured environment like Mongo doesn't make a lot of sense. We do realize many users are interested in this feature, and will continue to explore its possibility.

### # Why haven't you added this feature, or fixed that issue yet?

Gitaflow is primarily a free and open-source project, maintained by a small core team and community contributors who donate their time and resources.

Our platform is feature-rich, however we strictly adhere to our 80/20 Rule to avoid a messy/bloated codebase. Gitaflow is also quite stable, however new issues still arise, some of which may be triaged with a lower prioritization.

If you need, you can contact us about sponsoring expedited fixes or commissioning new features. You can also submit a pull request
(opens new window) — after all, it is open-source!

### # Can you give an ETA for this feature/fix?

If it is sponsored work, then yes, delivery dates are part of our statement of work agreements. Otherwise, most likely not. This is open-source software, work is prioritized internally, and all timelines are subject to change.

### # But this is an emergency, my very important project requires it now!

We understand, and are here to help. If you need something prioritized, you can reach out to us to discuss premium support, sponsoring expedited fixes or commissioning new features.