Today fullsend requires a billable GCP project for initial installation. The process for creating one is undocumented, but more importantly it requires:
- a project that your management would be willing to $ for
- getting management approval
- opening a helpdesk ticket (with required fields that many devs will have to guess at)
- waiting a day (or more?)
- a bunch of steps and GCP configuration that the average developer hasn't done before - i.e. 'complicated' and prone to error
Compare this to most external services where you can register and have access immediately until you hit some threshold (e.g. usage limit, private repos, etc).
This is a big barrier for initial trials and adoption by new teams: I can't easily test, try it on a repo, or play with it prior to setting up billing. At some point we should see if we can provide a free initial trial period, usage limits, ability to test agents against users-own repo, or some other mechanism where users can try out or initially install fullsend prior to getting their own project.
Today fullsend requires a billable GCP project for initial installation. The process for creating one is undocumented, but more importantly it requires:
Compare this to most external services where you can register and have access immediately until you hit some threshold (e.g. usage limit, private repos, etc).
This is a big barrier for initial trials and adoption by new teams: I can't easily test, try it on a repo, or play with it prior to setting up billing. At some point we should see if we can provide a free initial trial period, usage limits, ability to test agents against users-own repo, or some other mechanism where users can try out or initially install fullsend prior to getting their own project.