11–20 of 29 posts
How does Brex compare to Mercury?
If you signed up for Mercury today, you’d look at Brex and think, “Eugh, I should have signed up for Brex”.
A sweeping generalization is that Mercury and Brex are the same thing, but Brex is further ahead in terms of basic features to manage a small SaaS business. Mercury will hopefully deploy their capital to build out these features.
How does Brex compare to Mercury?
They're both good and much better than old-school banks like SVB / FRB etc. Brex also offers charge cards which Mercury doesn't (not sure if they have debit cards) so Brex has a broader set of things to offer. Satchel a SaaS buying-guide (kinda like Wirecutter for startups) wrote an in-depth guide here https://satchel.com/store-of-money/#recommendations and recommends Brex Cash.
How does Brex compare to Mercury?
They're both good and much better than old-school banks like SVB / FRB etc. Brex also offers charge cards which Mercury doesn't (not sure if they have debit cards) so Brex has a broader set of things to offer. Satchel a SaaS buying-guide (kinda like Wirecutter for startups) wrote an in-depth guide here https://satchel.com/store-of-money/#recommendations and recommends Brex Cash.
Earlier quoted context omitted.
The “bearer” prefix indicates the token is a “bearer” type token, as defined in RFC6750. As opposed to, for example, a “mac” token type. The bearer token can be a JWT, but can also be a different format of bearer token as long as it conforms to the requirements in the spec (ie, only certain characters are allowed). A “bearer” token means whoever has the token has authorization to perform the action. (Section 1.2 of t…
Isn't that just fancy phrasing for a username/password? Most APIs just have you set a key in the "Authorization" header. I don't get what value the "Bearer " prefix adds. That RFC is strange and seems it can be summarized in one line: Include header "Authorization: Bearer [API key]" for authenticating API calls.
Not quite. username/password authenticate who or what something is; bearer tokens permit what actions can be taken by the holder of that token, and tend to be short-lived in nature and ideally for very specific actions.
I'm curious as to what they used to do this. It's been a major pain point for me for five-odd years that Elixir Phoenix (don't know if Brex used Phoenix for this) doesn't have an OpenAPI autogenerator, and, now, this is my third job where I'm building an OpenAPI API in Elixir, so I got permission to open source our solution later this year.
Would have been nice to collaborate, but I guess Brex is leaving Elixir, so, there's that. They kind of had a bit of a reputation for not contributing much code back to the ecosystem =(
> One of the best decisions we made was to auto generate the OpenAPI specs from our code. I'm curious as to what they used to do this. It's been a major pain point for me for five-odd years that Elixir Phoenix (don't know if Brex used Phoenix for this) doesn't have an OpenAPI autogenerator , and, now, this is my third job where I'm building an OpenAPI API in Elixir, so I got permission to open source our solution lat…
> One of the best decisions we made was to auto generate the OpenAPI specs from our code. I'm curious as to what they used to do this. It's been a major pain point for me for five-odd years that Elixir Phoenix (don't know if Brex used Phoenix for this) doesn't have an OpenAPI autogenerator , and, now, this is my third job where I'm building an OpenAPI API in Elixir, so I got permission to open source our solution lat…
I no longer work at Brex, but I believe they did this using Kotlin rather than Elixir.