"We require a credit card on file before provisioning live API keys"
Err no thanks.
Launch HN: Kable (YC W22) – All-in-one platform for API products
71–80 of 84 posts
Re: Launch HN: Kable (YC W22) – All-in-one platform for API products
#72What’s the story for exporting data look like? E.g if I started with you but then wanted to migrate to a home grown solution.
There are a variety of different storage formats behind the curtain at Kable. Some things (like stored invoices) are trivial to export. Others (like full request histories) might be a bit more complicated. That said, we never want to lock you in. We will always support customers who need to export data out of Kable into another system.
Thanks for the response! I’m sure the question sounded basic but it’s really reassuring to read.
Re: Launch HN: Kable (YC W22) – All-in-one platform for API products
#73Earlier quoted context omitted.
There are a variety of different storage formats behind the curtain at Kable. Some things (like stored invoices) are trivial to export. Others (like full request histories) might be a bit more complicated. That said, we never want to lock you in. We will always support customers who need to export data out of Kable into another system.
Thanks for the response! I’m sure the question sounded basic but it’s really reassuring to read.
Of course! Our mission is to support developers building great products. Our goal is to help you grow, not hold you prisoner
Re: Launch HN: Kable (YC W22) – All-in-one platform for API products
#74Earlier quoted context omitted.
Have any example on how to add kable to a graphql API?
We don't currently have any customers using Kable and GraphQL together. To be totally honest, I'm not a GraphQL expert, and I don't want to give you any false information, so unfortunately no, I don't have an example for you. Kable can be accessed through our Node and Python libraries (more languages on the way) or over HTTPS REST API. I will have to defer to your design sense about the best way to leverage these tec…
One of the problems with graphql is a single query can fetch your entire API.
This means to record for billing, you would need to parse the AST and tag the parts as well as their associated cost in a query.
It's not an easy drop in, unfortunately.
Re: Launch HN: Kable (YC W22) – All-in-one platform for API products
#75Congratulations on your launch!
Re: Launch HN: Kable (YC W22) – All-in-one platform for API products
#76> Our pricing is pay-as-you-go based on the volume of events we store and the revenue we help our customers generate. That means we get to dogfood our own software for usage-based billing! So what is your pricing? The website says "starting at $200 / month", but before I go to sign up and try to integrate, I'd like to be able to estimate if it'd be $200/mo for my company or $2,000/mo. P.S.: I signed up, even got to a…
Non-public pricing is something that really grinds my gears...
The goal here is definitely not a lock-in strategy. Our lack of clear pricing is simply the nature of being a brand new company who hasn't yet had sufficient time to work with customers to solidify the right price point. As we iron out our business model we'll absolutely make pricing more transparent on our site.
Re: Launch HN: Kable (YC W22) – All-in-one platform for API products
#77"We require a credit card on file before provisioning live API keys" Err no thanks.
Our Test environment offers all of the functionality that our Live environment offers. You can get the entire Kable experience in the Test environment without registering a credit card. Only when you're ready to deploy Kable to your Live production environment do we require a payment method.
Re: Launch HN: Kable (YC W22) – All-in-one platform for API products
#78Earlier quoted context omitted.
Because it's Enterprise pricing. We price based on your company. If your logo is big enough, we'll give you cost price because we'll use you as a marketing tool. If you're a government client, we'll give it to you cheap enough to get a foothold in your organisation, then pull in massive deals over years and take away discounts once it's too hard to get rid of us. If you're some random company, you get sticker price -…
> If you're a government client, we'll give it to you cheap enough to get a foothold in your organisation, then pull in massive deals over years and take away discounts once it's too hard to get rid of us. This concerns me as a non-government agency. I hope vendor lock-in isn’t your business strategy.
Just making it clear for others as I had to double check.
The one you're replying to isn't op and is just taking a jab at enterprise pricing.
Re: Launch HN: Kable (YC W22) – All-in-one platform for API products
#79I'm the founder of Saasify, a similar platform from a few years back. Love what you guys are doing, though I think you may run into some of the same issues that we ran into. Here's our post-mortem that you'll hopefully find helpful https://transitivebullsh.it/saasify-vc-feedback
Immediately what I thought -- when your users become successful, they will churn. Ideally you want the opposite of that (expansion from successful users).
Re: Launch HN: Kable (YC W22) – All-in-one platform for API products
#80could be interesting if you added the option to also integrate their API with API aggregators -- write their integromate, zapier, pathfix, other blocks -- or at least give templates -- even templates would be good organic content: - how to add your API to Zapier - how to add your API to Integromat or whatever their new name (?) is - rinse & repeat for all the other fabrics - pathfix, mulesoft, etc.
Amazing idea, and actually something we're actively developing. Soon you'll be able to connect Kable to any of your other data sources through Segment. Then, if your application is hooked up to services like Zapier, Amplitude, Mixpanel, etc, you'll be able to funnel data into Kable for billing purposes with no additional code. Our goal here is to make it super easy to use Kable for billing no matter what your existin…
yes, my core thought was:
1. your current value prop is help users build API
2. value add is help them get distro for same API by abstracting away having their team deal with writing Zapier blocks, get into app stores for same, etc.
3. doing (2) is a long road, so could kickstart that with organic content for now, since a natural question after build API is ok, how do I get our block on their app store, same for integromat, mulesoft, etc.