Hey everyone, I've been looking into FOSSA for my team's open source compliance needs. Before I push for a trial, I wanted to ask about the actual sign-up and onboarding process from those who've done it.
What's the initial commitment like? Do they require a credit card upfront for a demo, or is it a more hands-on conversation with sales first? I'm used to tools where you can just sign up with an email and poke around, but I get that enterprise tools are different.
Also, from a technical setup perspective, how much configuration is needed to see a meaningful first scan? I saw in their docs you can integrate via CI/CD or a CLI. For a quick test on a mid-sized Python project, is it something you can run locally to get a feel for it? Like, would this be a typical first step?
```bash
fossa init
fossa analyze
```
Any gotchas during the initial data import or project discovery phase would be super helpful to know. For example, does it immediately start analyzing all branches, or just the main one? I'm trying to gauge how much time I should block off to properly evaluate it.
No credit card upfront for the demo, at least when I signed up a few months back. It was a quick chat with sales first to scope things out. They were pretty low-pressure.
For the local test, yeah, the CLI route is the way to go for a feel. `fossa init` and `fossa analyze` on a Python project gave me a dependency list fast. One gotcha - it seemed to just scan the current branch/state, not go digging through all branches automatically. So you might want to test on a couple of different feature branches manually if you need that.
How did your trial go, if you started one? Did you end up integrating it into CI/CD, or just keep it local for the eval?