WEBVTT

NOTE
This file was generated by Descript 

00:00:00.269 --> 00:00:01.409
. Mike Bifulco: Hey friends, Mike from NPI.

00:00:01.439 --> 00:00:03.599
As you won't hate here
chiming in from the future.

00:00:03.929 --> 00:00:07.159
I messed up during this interview there's
about five minutes of this interview

00:00:07.159 --> 00:00:11.209
at the very beginning where I am using
the microphone on my earbuds to record.

00:00:11.209 --> 00:00:12.439
And you can really tell.

00:00:12.749 --> 00:00:14.459
So I apologize for that in advance.

00:00:14.489 --> 00:00:17.189
But I promise I did my best
to make it better using all

00:00:17.189 --> 00:00:18.689
the tools available at my.

00:00:19.089 --> 00:00:22.099
Disposal using AI and audacity
and things like that to make

00:00:22.099 --> 00:00:23.569
the audio a little nicer.

00:00:23.599 --> 00:00:26.779
It's as good as it can be roughly
given the skills that I have, but

00:00:26.999 --> 00:00:27.929
I just figured I'd let you know.

00:00:27.929 --> 00:00:30.779
The entire interview is not as
miserable sounding on my end.

00:00:30.879 --> 00:00:31.989
As it seems at the beginning.

00:00:32.019 --> 00:00:35.329
So zip ahead if you need to, but
otherwise enjoy the interview and thanks

00:00:35.329 --> 00:00:36.559
for watching the indoor listening.

00:00:37.660 --> 00:00:38.470
riverside_mike_bifulco_raw-synced-video-cfr_podcast_recording w_0027:
Welcome back to another

00:00:38.470 --> 00:00:39.820
episode of APIs you won't Hate.

00:00:39.910 --> 00:00:40.930
My name is Mike Bico.

00:00:40.930 --> 00:00:42.700
I'm one of the co-founders
of APIs You Won't hate.

00:00:42.700 --> 00:00:45.190
And I'm excited to sit down
today for an interview.

00:00:45.190 --> 00:00:47.620
Stand up today for an interview,
whatever, hop on the internet for an

00:00:47.620 --> 00:00:51.205
interview with my my old pal James
Perkins to talk about what he's building.

00:00:51.235 --> 00:00:53.295
And James, it's really nice
to have you on the show today.

00:00:53.295 --> 00:00:55.875
I'm, I'm interested to hear about
UN Key and your story there.

00:00:55.905 --> 00:00:56.895
Thanks a ton for joining us.

00:00:56.895 --> 00:00:57.315
How are you doing?

00:00:57.650 --> 00:00:58.380
riverside_james_raw-synced-video-cfr_podcast_recording w_0028:
Yeah, I'm good.

00:00:58.380 --> 00:00:59.300
Thanks for having me.

00:00:59.470 --> 00:01:01.125
It's been a while since we've talked.

00:01:01.645 --> 00:01:03.445
Yeah, I'm, I'm happy to be here.

00:01:03.445 --> 00:01:05.965
Happy to chat about UN key and what
we're building and how we're trying

00:01:05.965 --> 00:01:09.955
to make APIs suck a lot less than
they, they do most of the time.

00:01:10.480 --> 00:01:11.710
riverside_mike_bifulco_raw-synced-video-cfr_podcast_recording w_0027:
Oh, you found yourself in the right

00:01:11.710 --> 00:01:13.210
place then I think for that discussion.

00:01:13.760 --> 00:01:16.670
James, you and I have sort of a
serendipitous internet relationship.

00:01:16.670 --> 00:01:19.085
I feel like every time I turn
a corner online you're poking

00:01:19.085 --> 00:01:20.165
your head around saying, hi.

00:01:20.215 --> 00:01:22.495
I, I don't remember exactly where
we met, but I know we crossed

00:01:22.495 --> 00:01:23.845
paths a bit while I was at Stripe.

00:01:23.845 --> 00:01:23.905
I.

00:01:24.230 --> 00:01:26.750
Doing developer relations there
and later while you were doing

00:01:26.750 --> 00:01:29.170
developer relations and now you're
starting and building a product.

00:01:29.170 --> 00:01:31.060
So I, I'd love maybe if you
start just giving us, like,

00:01:31.060 --> 00:01:32.080
the lowdown on your career.

00:01:32.080 --> 00:01:34.340
How did you find your way
to what you're doing now?

00:01:34.340 --> 00:01:35.480
And then let's talk a little bit about.

00:01:36.170 --> 00:01:36.980
riverside_james_raw-synced-video-cfr_podcast_recording w_0028:
Yeah, for sure.

00:01:36.980 --> 00:01:39.440
So I've been around a really long time.

00:01:39.440 --> 00:01:42.740
I think if my co-founder listens to this,
I'm really sorry, but I have to do this.

00:01:42.800 --> 00:01:44.600
So I've been around for 16 years.

00:01:44.650 --> 00:01:50.165
I started way back doing Java development
for a few different companies.

00:01:50.585 --> 00:01:54.455
First one was like a really small stage
startup that did online registration.

00:01:54.455 --> 00:01:57.245
So in America, if you buy a car
and you get from the dealership.

00:01:57.515 --> 00:02:00.245
And they give you like a temp tag
in the dealership or the actual

00:02:00.245 --> 00:02:01.415
tags depending on where you live.

00:02:01.875 --> 00:02:04.185
That software was built by
me and a, and a few people.

00:02:04.675 --> 00:02:08.095
And then I moved on to things
like gambling and the lottery.

00:02:08.145 --> 00:02:13.245
Did that for a while, did digital banking,
then I moved on to FinTech startups.

00:02:13.575 --> 00:02:17.955
Tina CMS was my real break into
where people really know me.

00:02:18.765 --> 00:02:21.465
That's when I started doing
developer relations and doing all

00:02:21.465 --> 00:02:24.945
the sorts of YouTubes and podcasts
and all the other things that

00:02:24.945 --> 00:02:26.415
I've done throughout my career.

00:02:26.955 --> 00:02:32.455
And then the real thing that everyone
really knows me for was Clark which is

00:02:32.605 --> 00:02:36.485
where I've met a lot of different people
across, across different industries.

00:02:36.485 --> 00:02:37.925
I think that's how we actually met.

00:02:38.590 --> 00:02:39.465
riverside_mike_bifulco_raw-synced-video-cfr_podcast_recording w_0027:
I think it may be, yeah.

00:02:39.725 --> 00:02:41.375
riverside_james_raw-synced-video-cfr_podcast_recording w_0028:
I think you were working on a project

00:02:41.375 --> 00:02:44.285
with Clark and you had questions
and then I think, you know, bouncing

00:02:44.285 --> 00:02:47.555
around and then, you know, you moved
on to, to what you're doing now.

00:02:47.560 --> 00:02:49.055
And we chatted a bit about that.

00:02:49.515 --> 00:02:51.525
But yeah, that's most of my career.

00:02:51.555 --> 00:02:57.650
And then I left Clark in September
which is when the funding for Key was

00:02:57.740 --> 00:02:59.930
basically almost finished at that point.

00:02:59.990 --> 00:03:02.600
We, we got a few checks in,
but we were still finishing up.

00:03:02.660 --> 00:03:04.100
And then that was when I went full time.

00:03:04.835 --> 00:03:05.125
riverside_mike_bifulco_raw-synced-video-cfr_podcast_recording w_0027:
Yeah.

00:03:05.150 --> 00:03:05.540
Got it.

00:03:05.540 --> 00:03:05.900
Wow.

00:03:06.140 --> 00:03:07.010
Well, quite the career.

00:03:07.040 --> 00:03:08.720
You've, you've touched many industries.

00:03:08.720 --> 00:03:12.230
You know, like, like I guess a lot
of successful developers tend to do

00:03:12.280 --> 00:03:15.380
getting your fingers deep in all sorts
of problems and getting your hands

00:03:15.380 --> 00:03:17.510
dirty with all, all sorts of industries.

00:03:17.840 --> 00:03:20.240
I guess that brings us to sort of
present day and maybe September

00:03:20.240 --> 00:03:23.855
of 2023, when, when un key sort of
raised you round, but also started

00:03:23.855 --> 00:03:25.960
making the presence online known.

00:03:26.010 --> 00:03:27.030
Why don't you tell us about UN key?

00:03:27.030 --> 00:03:27.780
What's the story there?

00:03:28.310 --> 00:03:30.880
riverside_james_raw-synced-video-cfr_podcast_recording w_0028:
Yeah, so on Key is essentially a.

00:03:31.560 --> 00:03:36.300
API management platform that we're kind of
redefining what API management is and how

00:03:36.300 --> 00:03:38.280
it's built and how we're using it today.

00:03:38.280 --> 00:03:42.150
So if you think about API management
platforms today, you're talking things

00:03:42.150 --> 00:03:48.150
like Kong or Tyke or even, you know,
Google's offering or AWS is offering

00:03:48.150 --> 00:03:49.470
through gateways and things like that.

00:03:50.280 --> 00:03:55.260
And when we were building APIs,
just in general, my co-founder

00:03:55.350 --> 00:03:56.700
just built a bunch of APIs.

00:03:56.700 --> 00:03:57.870
I've done it throughout my career.

00:03:57.870 --> 00:04:00.450
We found that it was hard.

00:04:00.810 --> 00:04:04.470
To protect that API,
however that might be.

00:04:04.470 --> 00:04:08.010
Whether it was through giving people
API keys 'cause you want them to be

00:04:08.010 --> 00:04:12.810
able to interact with it or rate limit
that API endpoint for some reason, or

00:04:13.020 --> 00:04:15.720
it was just a bunch of things that you
don't think about until you've already

00:04:15.720 --> 00:04:18.840
built the API and then it's like, oh,
I need to do this and this and this,

00:04:19.200 --> 00:04:20.940
and there was no easy way to do that.

00:04:20.970 --> 00:04:22.800
It was all or nothing.

00:04:23.520 --> 00:04:29.280
It was, you need the entire gateway to
do a one API key for a user, or you need

00:04:29.280 --> 00:04:33.360
to, you know, do some sort of ridiculous
amount of work to make it globally

00:04:33.360 --> 00:04:34.800
distributed or whatever it might be.

00:04:34.800 --> 00:04:38.580
Or you build it in-house, which is where
we find some people are still doing.

00:04:40.020 --> 00:04:45.460
So we kind of had this idea
originally to be a blog post for

00:04:45.460 --> 00:04:48.880
Clark and UPS Dash because my
co-founder used to work at UPS Dash.

00:04:49.270 --> 00:04:52.840
We were like, Hey, we could just
build a blog post around globally

00:04:52.840 --> 00:04:57.490
distributed API keys that would like
used Clark, and then used up dash.

00:04:57.490 --> 00:05:00.340
And then basically you link them together
and then you give them an API key and

00:05:00.345 --> 00:05:01.510
then you can kind of work with it.

00:05:02.230 --> 00:05:05.230
And after about 10 minutes of talking,
I was like, no, this is just a business

00:05:05.230 --> 00:05:09.010
idea that I think there's actually
a business idea that we could build.

00:05:09.700 --> 00:05:11.140
And then the rest is really history.

00:05:11.140 --> 00:05:13.180
We, for the first commit was in June.

00:05:14.110 --> 00:05:20.200
The beginning of June, we launched at
the end of June, and then everything

00:05:20.200 --> 00:05:21.790
else has been a rocket ship since then.

00:05:21.900 --> 00:05:25.950
Lots of users, lots of feedback,
lots of different iterations, lots of

00:05:25.950 --> 00:05:29.130
improvements, lots of new features,
you know, all the stuff you kind of do

00:05:29.130 --> 00:05:30.510
when you're in a small stage startup.

00:05:31.030 --> 00:05:34.955
And then we raised our fund, which
was the weirdest thing I've ever done.

00:05:35.005 --> 00:05:37.105
Worked in all these startups,
never seen the other side, and

00:05:37.105 --> 00:05:38.425
now I understand how that works.

00:05:38.725 --> 00:05:42.565
Yeah, it was really, really crazy and
it was just like you know, let's try us

00:05:42.565 --> 00:05:43.885
out and see what happens, kind of thing.

00:05:43.885 --> 00:05:45.145
And here we are today.

00:05:46.075 --> 00:05:49.345
Mike Bifulco: So the rocket ship metaphor
is definitely something that sounds apt

00:05:49.345 --> 00:05:51.415
given the path you've taken to get here.

00:05:51.685 --> 00:05:55.415
And I am also living on the the,
the raising money side of the

00:05:55.415 --> 00:05:56.615
founder story for the first time.

00:05:56.615 --> 00:05:57.905
So I can definitely relate to that.

00:05:58.005 --> 00:05:59.385
If you're listening to
this and you haven't.

00:05:59.580 --> 00:06:01.950
Raised money for, for a project
of your own at some point.

00:06:01.980 --> 00:06:05.290
It definitely changes the way you think
about things and requires a pro, a

00:06:05.290 --> 00:06:08.830
project, a problem, an audience that
can hit a certain level of scale.

00:06:08.830 --> 00:06:12.250
And so hopefully the rocket ship that
you've now strapped yourself to is headed

00:06:12.250 --> 00:06:15.030
in a direction where that scale is really
important really important and also

00:06:15.075 --> 00:06:15.495
James: Right.

00:06:15.675 --> 00:06:16.035
Yep.

00:06:16.390 --> 00:06:18.100
Mike Bifulco: What I'm really
curious about there then is like,

00:06:18.100 --> 00:06:19.660
this is a pretty big problem space.

00:06:19.660 --> 00:06:23.270
Like building API management is
not a, a you know, a small rock

00:06:23.300 --> 00:06:25.180
in project manager parlance.

00:06:25.400 --> 00:06:27.080
What was the first cut at this?

00:06:27.080 --> 00:06:29.030
Like, what, what was the first
thing you built to prove that you

00:06:29.030 --> 00:06:30.050
had something that people would

00:06:30.110 --> 00:06:34.130
James: Yeah, so the first thing,
so we decided to go in reverse.

00:06:34.280 --> 00:06:39.230
So with all these companies, basically
doing all or nothing, it was do a gateway

00:06:39.230 --> 00:06:40.565
and then you can have these features.

00:06:41.435 --> 00:06:44.285
We decided that the best idea was
to give people what they actually

00:06:44.285 --> 00:06:46.325
wanted, which was just API keys.

00:06:46.865 --> 00:06:50.225
If you're a small startup, a small
business, medium sized business, maybe

00:06:50.225 --> 00:06:54.155
even a large business, you probably
don't need a gateway because you can

00:06:54.155 --> 00:06:55.985
probably handle most of the infra.

00:06:55.990 --> 00:06:59.615
If you're using serverless, for example,
like you can scale your infra pretty well

00:06:59.615 --> 00:07:03.515
without having to worry too much about
the other features that Gateway brings.

00:07:04.025 --> 00:07:09.155
So the first iteration
was API Keys that had.

00:07:09.980 --> 00:07:11.360
Per key analytics.

00:07:11.480 --> 00:07:14.390
So anytime a key was used, you
had the analytical data that you

00:07:14.390 --> 00:07:17.660
needed to figure out, you know,
was it a successful request?

00:07:17.665 --> 00:07:18.560
Was it rate limited?

00:07:18.560 --> 00:07:19.820
Was it use, succeeded?

00:07:19.820 --> 00:07:23.000
Like a few things, but
you could do it per key.

00:07:23.000 --> 00:07:26.510
So you could really deep, deep dive into
your analytics as you were building.

00:07:27.740 --> 00:07:28.970
And that was the first iteration.

00:07:28.975 --> 00:07:32.840
So we had rate limiting keys
that expired by a certain day.

00:07:33.200 --> 00:07:37.340
And then we had key, the keys
you could attach data to.

00:07:37.340 --> 00:07:42.470
So owner id, metadata was all an option
that you could just attach to a key and we

00:07:42.475 --> 00:07:44.090
would return that data if you needed it.

00:07:44.660 --> 00:07:48.560
And it was, you could create
a key, you could delete a

00:07:48.560 --> 00:07:49.940
key and you could verify key.

00:07:49.940 --> 00:07:50.450
And that was it.

00:07:50.630 --> 00:07:52.070
That was the first iteration.

00:07:52.310 --> 00:07:56.060
It had a dashboard that had very
rudimentary analytical data on it.

00:07:56.370 --> 00:07:59.690
And that, that was basically V
zero that we shipped in June.

00:08:00.215 --> 00:08:03.815
Then we slowly iterated on things that
we thought people needed at the time.

00:08:05.855 --> 00:08:06.275
Mike Bifulco: Yeah.

00:08:06.860 --> 00:08:11.280
I can imagine just from that first set
of features quite a bit of value, right?

00:08:11.280 --> 00:08:13.920
Possible or at least promise
of value possible for folks.

00:08:14.460 --> 00:08:17.580
From everything from just proving that
like, hey, someone is using my API, this

00:08:17.580 --> 00:08:21.210
person is using my API over and over is
a good signal for lots of teams building

00:08:21.210 --> 00:08:25.270
API products, but also preventing abuse
or things like that and, and looking

00:08:25.270 --> 00:08:26.500
at where costs are being driven up.

00:08:26.560 --> 00:08:27.310
That's super cool.

00:08:27.930 --> 00:08:31.040
How did you, well, I, I guess
you are, someone who's been on

00:08:31.040 --> 00:08:32.240
the internet for a long time.

00:08:32.290 --> 00:08:34.360
I'm curious like how you found
your first audience for this.

00:08:34.360 --> 00:08:34.660
How were you

00:08:34.830 --> 00:08:38.850
James: Yeah, so we, both of
us are quite known on Twitter

00:08:38.850 --> 00:08:40.320
for different various things.

00:08:40.320 --> 00:08:44.130
Like my co-founder is very well known
for like open source projects and

00:08:44.130 --> 00:08:47.520
building a lot of stuff, and I'm very
much known for like the YouTube stuff

00:08:47.520 --> 00:08:48.990
and Clark and a few other things.

00:08:48.990 --> 00:08:52.620
So when we launched the
product, we did a single tweet.

00:08:54.030 --> 00:08:57.660
A single video, which were
spaced out like a day apart.

00:08:58.220 --> 00:09:03.800
And that really like gave us the I
that actually solidified when we did

00:09:03.800 --> 00:09:07.100
the launch in June, that solidified
the fact that we were gonna raise

00:09:07.340 --> 00:09:11.960
money because we were getting signals
from other founders that we knew in

00:09:11.960 --> 00:09:15.170
the industry saying like, Hey, this is
actually something that people need.

00:09:15.590 --> 00:09:17.780
Because the original project
was just a side project.

00:09:17.780 --> 00:09:19.280
It was just something we
wanted to build together.

00:09:20.150 --> 00:09:22.280
We weren't even charging
people at the time.

00:09:22.340 --> 00:09:23.630
It was all open source.

00:09:23.960 --> 00:09:27.380
It was just like a fun project for
us to build over like a few weeks.

00:09:27.810 --> 00:09:32.940
And when we did the tweet, it
did like 150,000 impressions.

00:09:33.480 --> 00:09:35.310
It brought us like 700 users.

00:09:35.490 --> 00:09:38.550
Some of those users were just, you
know, people checking out the platform.

00:09:38.820 --> 00:09:41.310
Some of them were actual people
that wanted to try the platform.

00:09:41.910 --> 00:09:44.820
And then, yeah, just a bunch of
feedback came through that about

00:09:44.940 --> 00:09:46.650
like, Hey, this is a cool idea.

00:09:46.650 --> 00:09:48.180
This is really something we need.

00:09:48.690 --> 00:09:52.980
No one's really done globally distributed
API keys before, like, how does that work?

00:09:52.980 --> 00:09:55.170
And it was very much like, oh,
here's the open source project.

00:09:55.170 --> 00:09:56.850
You can go and look and
see how we're building it.

00:09:57.330 --> 00:10:01.200
And then that brought in some
of our first real users and real

00:10:01.200 --> 00:10:02.400
contributions at that point.

00:10:02.685 --> 00:10:05.395
Mike Bifulco: I can imagine those
things adding up pretty quickly to

00:10:05.400 --> 00:10:06.715
be the signals you would wanna see.

00:10:06.995 --> 00:10:09.785
Had you been entertaining the idea of
building this into something larger?

00:10:09.785 --> 00:10:11.545
Were you just hoping to get the open

00:10:11.545 --> 00:10:11.785
James: No.

00:10:11.965 --> 00:10:14.305
Yeah, we were basically like,
cool, this is a cool side project

00:10:14.305 --> 00:10:15.805
that we can work on together.

00:10:15.865 --> 00:10:19.255
Andreas and I had never met outside
of the internet, like Discord and

00:10:19.260 --> 00:10:23.065
stuff like that, and we were both
very happy with the roles that we had.

00:10:23.065 --> 00:10:25.765
Like I was super happy at Clark,
he was super happy at Up Stash.

00:10:25.765 --> 00:10:28.105
So we used this as more of
an opportunity of just like

00:10:28.465 --> 00:10:31.585
working together, collaborating,
building something, having fun.

00:10:32.155 --> 00:10:37.225
And even when we were being approached
by VCs, we have a discord message

00:10:37.225 --> 00:10:40.705
that we both have the image of,
that we occasionally just randomly

00:10:40.705 --> 00:10:44.155
share in our slack now, which is
just us saying like, no, I'm good.

00:10:44.155 --> 00:10:45.025
Part-times fine.

00:10:45.025 --> 00:10:46.435
Like, I'd rather do this part-time.

00:10:46.435 --> 00:10:47.335
I'm happy with my job.

00:10:47.695 --> 00:10:50.345
And yeah, we like, we like to remind
ourselves of that occasionally.

00:10:50.637 --> 00:10:51.207
Mike Bifulco: It seems like,

00:10:51.267 --> 00:10:53.007
uh, the universe had
different plans for you.

00:10:53.417 --> 00:10:54.917
Signals like that are hard to ignore.

00:10:54.917 --> 00:10:55.577
Certainly.

00:10:55.917 --> 00:10:58.167
And I guess, so at this
point, that was last June.

00:10:58.197 --> 00:11:02.237
This would be, we're we're recording in
early May, I guess you'd call it of 2024.

00:11:02.387 --> 00:11:03.797
So it's been almost a year.

00:11:04.047 --> 00:11:07.287
I'm, I'd imagine you've had several
chapters of existence since then.

00:11:07.397 --> 00:11:10.577
So tell me, tell me how things sort of
fared since then and where you're at

00:11:10.607 --> 00:11:13.787
James: so we're definitely a lot
different than where we were.

00:11:14.027 --> 00:11:16.547
The core product still
lies a lot in API keys.

00:11:17.252 --> 00:11:21.752
Except from now we have a lot more
features and we're expanding into more of

00:11:21.752 --> 00:11:23.432
the API management platform in general.

00:11:23.882 --> 00:11:26.192
So we can talk about keys first
and then we can talk about some

00:11:26.192 --> 00:11:27.272
of the other stuff we've done.

00:11:27.272 --> 00:11:31.442
So the keys, now we, with the
feedback that we've got through

00:11:31.472 --> 00:11:35.642
customers and just generalized
people, we've added other features.

00:11:35.642 --> 00:11:40.632
For example, now you can do keys with
rate limiting that are cost based.

00:11:40.632 --> 00:11:41.052
So.

00:11:41.877 --> 00:11:45.747
If you've got like a specific endpoint
that you need to rate, limit cost-wise,

00:11:45.747 --> 00:11:50.997
because maybe it's an expensive resource
that maybe it's an AI project and you

00:11:50.997 --> 00:11:54.657
are giving keys out, you can, you can
actually say, Hey, this is gonna cost

00:11:55.047 --> 00:11:59.517
three instead of the usual one for a
rate limit so that you can kind of push

00:11:59.517 --> 00:12:03.267
around and, and make sure that like
your expensive resources aren't being

00:12:03.267 --> 00:12:06.267
abused as much as like a cheap resource
where you're just looking something up.

00:12:06.817 --> 00:12:09.007
We also have keys that now have.

00:12:09.412 --> 00:12:10.222
Usage base.

00:12:10.227 --> 00:12:13.252
So you can just say this key has 100 uses.

00:12:13.912 --> 00:12:16.492
After that a hundred uses, you
can no longer use it anymore.

00:12:16.672 --> 00:12:21.682
Basically, the only way that it
can be reused is if the developer

00:12:21.682 --> 00:12:23.062
then goes and does an update.

00:12:23.062 --> 00:12:28.342
So it works really well for token
based usage or you know, a monthly

00:12:28.342 --> 00:12:31.432
subscription that you get a hundred
uses of anything like that where you

00:12:31.432 --> 00:12:35.032
really just wanna limit the amount
that someone can use A key, and then

00:12:35.032 --> 00:12:38.882
we've introduced audit logging and
we've introduced better analytics.

00:12:38.882 --> 00:12:41.282
So like it's more rich
in your analytical data.

00:12:41.672 --> 00:12:44.942
We've added API endpoints so that you
can pull the analytical data yourself

00:12:44.947 --> 00:12:47.882
and then build your drone dashboards
or build whatever you need there.

00:12:48.512 --> 00:12:51.332
And that's kind of how we're
fit in, in, into the key space.

00:12:51.337 --> 00:12:52.207
So that's still the core.

00:12:53.147 --> 00:12:57.857
Real core part of UN key, and it'll always
be core regardless if we, you know, once

00:12:57.857 --> 00:13:01.127
we get into gateways and things like that,
it'll still be core part of our products.

00:13:01.637 --> 00:13:04.037
And then we introduced standalone
rate limiting this year.

00:13:04.517 --> 00:13:08.747
So if you've ever had like A-T-R-P-C
route or something like that, that you

00:13:08.752 --> 00:13:12.017
just want to rate limit, but you don't
really need public API Keys or something

00:13:12.017 --> 00:13:17.197
like that, you can do that with UN key
and it will just be globally distributed.

00:13:17.197 --> 00:13:18.607
So it'll be really, really fast.

00:13:19.132 --> 00:13:21.352
And you can choose how you want to use it.

00:13:21.352 --> 00:13:24.292
So we have two options, which
is synchronous requests.

00:13:24.292 --> 00:13:27.982
So that obviously you have to wait for us
to actually respond and say, Hey, yeah,

00:13:27.982 --> 00:13:31.792
they're good, or they're bad, or you can
use our asynchronous version, which you

00:13:31.792 --> 00:13:33.892
just give up a small amount of accuracy.

00:13:34.432 --> 00:13:37.852
So our anchor accuracy is
like 98%, even with Async.

00:13:38.372 --> 00:13:41.252
That will just be like, yep,
I, we, we believe this is good.

00:13:41.492 --> 00:13:44.192
We assume that this is good based
upon like the data that we have.

00:13:44.532 --> 00:13:47.652
So you can have a really, really
fast rate limiting system and

00:13:47.657 --> 00:13:49.092
that's fully globally distributed.

00:13:49.092 --> 00:13:54.762
It has things like overrides, so if you've
got a specific user or maybe an IP address

00:13:55.152 --> 00:14:00.072
that they need higher limits because maybe
you have a deal in place or maybe you

00:14:00.072 --> 00:14:03.822
know it's an internal user or whatever
it might be, you can manually override.

00:14:04.527 --> 00:14:08.307
In our dashboard and say like,
Hey, if this user comes through,

00:14:08.937 --> 00:14:10.017
they have higher limits.

00:14:10.077 --> 00:14:11.667
Don't use the usual ones.

00:14:11.667 --> 00:14:13.467
And you don't have to
make any code changes.

00:14:13.467 --> 00:14:15.717
We'll just say, okay, yep,
this person is coming through.

00:14:16.017 --> 00:14:16.437
Cool.

00:14:16.527 --> 00:14:20.037
All right, let's give them these limits
instead and let's check against those.

00:14:20.457 --> 00:14:23.547
So basically it gives you this
really big amount of flexibility

00:14:23.547 --> 00:14:24.927
around how you wanna rate limit.

00:14:25.587 --> 00:14:29.127
And those are the big main features that
we've added, like since the beginning.

00:14:29.817 --> 00:14:32.967
We've had lots of iterations behind
the scenes of different code base and

00:14:32.967 --> 00:14:37.017
like we've changed the way that we
do keys and what providers we use.

00:14:37.017 --> 00:14:40.227
And we were originally on servers
and now we're all serverless.

00:14:40.227 --> 00:14:42.777
Like we did a bunch of stuff
to like really optimize how

00:14:42.777 --> 00:14:44.187
fast we could we could get it.

00:14:44.607 --> 00:14:47.252
And yeah, we're really happy
with where we're sat right now.

00:14:49.637 --> 00:14:53.987
Mike Bifulco: Certainly, it's a very
interesting set of features because you've

00:14:53.987 --> 00:14:57.587
added a few things that very quickly
give any product that takes advantage

00:14:57.587 --> 00:14:59.417
of it, like a much more polished feel.

00:14:59.757 --> 00:15:02.037
And from, from my perspective,
they're pretty hard to build.

00:15:02.097 --> 00:15:04.017
Those are things that
you would probably need.

00:15:04.017 --> 00:15:06.507
If I was going to build that for scratch
for an API product, it would take.

00:15:07.002 --> 00:15:10.422
Dozens of hours of engineering
time and probably revisits every

00:15:10.422 --> 00:15:12.252
so often when I un uncover a bug.

00:15:12.592 --> 00:15:16.497
And, and is the kind of thing that
in a world where a AI based products

00:15:16.497 --> 00:15:20.007
are becoming more and more valuable
those features are super important.

00:15:20.067 --> 00:15:23.367
Like being able to have a customer that
gets advanced access or faster access

00:15:23.372 --> 00:15:24.687
is something that's really massive.

00:15:25.297 --> 00:15:27.457
That's, that's a, a, a
great set of features.

00:15:27.457 --> 00:15:30.187
And I, I like that it's like
fairly minimal, but provides,

00:15:30.217 --> 00:15:33.307
I mean, immeasurable value to,
to teams that really need it.

00:15:33.457 --> 00:15:33.667
That's

00:15:33.712 --> 00:15:34.342
James: Y Yeah.

00:15:34.342 --> 00:15:40.822
Our whole focus was really around like
how as a, as a developer, if I get

00:15:40.822 --> 00:15:44.002
this product, do I need everything
or do I need specific things?

00:15:44.002 --> 00:15:44.302
Right.

00:15:44.302 --> 00:15:48.052
And the, the, the problem usually
lies that you get everything,

00:15:48.052 --> 00:15:48.892
even though you don't want it.

00:15:49.717 --> 00:15:52.447
Then you're like, oh man, I'm
paying for stuff I'm not even using.

00:15:52.447 --> 00:15:55.117
Or man, I have to implement this
because of the way that it works.

00:15:55.537 --> 00:15:59.587
We are, we are really focusing on like,
Hey, here's a package for rate limiting.

00:15:59.587 --> 00:16:00.187
Just use it.

00:16:00.757 --> 00:16:04.567
Here's a package that gives you the
entire API use that, and then issue

00:16:04.567 --> 00:16:06.127
keys, create keys, do whatever you want.

00:16:06.517 --> 00:16:10.717
We want people to have the option to
pick the features they want versus being

00:16:10.717 --> 00:16:12.457
forced to use features they don't need.

00:16:12.725 --> 00:16:16.350
Mike Bifulco: It makes a ton of sense
and it lets people bite off a, a size

00:16:16.350 --> 00:16:18.660
of the product that they want to use
and that makes sense for their business.

00:16:18.660 --> 00:16:21.610
And hopefully one of the things I
like about businesses like this is

00:16:21.610 --> 00:16:24.820
that as you are, your customers are
successful, you become more successful,

00:16:24.850 --> 00:16:26.230
you know, as they get more use or more.

00:16:26.620 --> 00:16:28.560
People driving their
product and revenue up.

00:16:28.560 --> 00:16:31.110
Then you're, you're benefiting as
well, invariably because they're using

00:16:31.110 --> 00:16:33.070
more of on key and everyone wins.

00:16:33.070 --> 00:16:36.450
That's, that's aligning incentives,
which is always a good sign too.

00:16:37.140 --> 00:16:39.570
I'm, I'm curious to hear a little
bit about your first customers or

00:16:39.570 --> 00:16:41.370
maybe your first year of customers.

00:16:41.370 --> 00:16:43.200
Like what are the use cases
that stand out to you?

00:16:43.200 --> 00:16:46.060
How did you find your, find
your way into people's hearts

00:16:46.060 --> 00:16:47.230
as a, a product that they should

00:16:47.365 --> 00:16:48.115
James: Yeah, for sure.

00:16:48.565 --> 00:16:54.445
I'd love our first ever customer was
a crypto trading platform, which is

00:16:54.445 --> 00:16:57.655
like odd and also kind of interesting.

00:16:57.660 --> 00:17:00.355
So they were a crypto trading platform.

00:17:00.665 --> 00:17:01.595
The name is Premier.

00:17:02.115 --> 00:17:05.445
They were building an API and
we launched pricing right as

00:17:05.445 --> 00:17:06.495
they were doing their API.

00:17:07.515 --> 00:17:09.195
So we're like, Hey, we're
actually gonna charge for this.

00:17:09.195 --> 00:17:10.155
Here's the pricing.

00:17:10.155 --> 00:17:13.515
If you know, we'll, we'll happily
talk if you're doing big volumes,

00:17:13.965 --> 00:17:16.575
thinking like, no one's gonna
do big volumes on this platform.

00:17:16.575 --> 00:17:18.225
No one's ever heard of
them before kind of thing.

00:17:18.825 --> 00:17:22.035
And they've been our biggest
customer since basically day one.

00:17:22.195 --> 00:17:24.440
They do millions of requests a month.

00:17:24.920 --> 00:17:26.090
They're pretty popular.

00:17:26.140 --> 00:17:29.960
They drive a lot of like, resources
and we see them, you know, spike

00:17:29.960 --> 00:17:33.740
when crypto spikes and they
dip down when crypto dips down.

00:17:33.740 --> 00:17:36.770
So we're like, we can see when runs are
happening 'cause like our usage will

00:17:36.770 --> 00:17:38.360
spike and then it will dip back down.

00:17:39.050 --> 00:17:39.340
Mike Bifulco: Sure.

00:17:39.430 --> 00:17:41.860
James: they were an interesting
first customer and also just an

00:17:41.860 --> 00:17:43.000
interesting customer in general.

00:17:43.000 --> 00:17:46.810
Like thinking about how web free is
all decentralized and then using a

00:17:46.810 --> 00:17:50.950
centralized system for your API keys
was something that we were still

00:17:50.950 --> 00:17:52.600
struggling to wrap our head around a bit.

00:17:53.020 --> 00:17:55.630
But yeah, they've always been,
they've been super happy with the

00:17:55.630 --> 00:17:57.610
platform since basically July.

00:17:57.970 --> 00:18:02.020
And then a lot of AI customers
coming in where they're building,

00:18:02.470 --> 00:18:06.640
you know, those AI products that
need either API keys or, or something

00:18:06.645 --> 00:18:09.220
to kind of help them drive forward.

00:18:09.640 --> 00:18:13.780
And it's been interesting to see
there that a large majority of our

00:18:13.780 --> 00:18:18.280
actual customer base that are paying
customers are in the AI space.

00:18:18.670 --> 00:18:20.590
So it's usually ai.

00:18:20.650 --> 00:18:24.400
And then we have a few Web3 customers,
one of them being the crypto trading

00:18:24.400 --> 00:18:25.570
platform and a couple others.

00:18:26.050 --> 00:18:31.510
And then we have others like
cal.com uses UN key to power their

00:18:31.510 --> 00:18:33.070
rate limiting behind the scenes.

00:18:33.430 --> 00:18:35.830
Which is, they're, they're
a newer, newer customer.

00:18:35.830 --> 00:18:37.060
They were fairly recent.

00:18:37.530 --> 00:18:41.370
And then we've just had some side projects
where they've come in and been like, I

00:18:41.370 --> 00:18:46.170
was building an A API and it would've
taken me six months to do this work, but

00:18:46.500 --> 00:18:48.450
with you guys, it took me like a week.

00:18:48.880 --> 00:18:51.425
And most of that was just like
me spinning up API endpoints and

00:18:51.425 --> 00:18:52.865
then introducing on Key into that.

00:18:53.130 --> 00:18:54.750
And that, that's basically
been our customer base.

00:18:54.750 --> 00:18:59.130
And then people check us out fairly
regularly, like two, 300 people a

00:18:59.130 --> 00:19:02.160
month come in and check us out and,
and play around with the platform

00:19:02.165 --> 00:19:04.170
and, and see kind of what we're doing.

00:19:04.645 --> 00:19:06.745
But yeah, that's been
most of our customer base.

00:19:06.745 --> 00:19:09.580
And then we have some other open
source friends that also use us for

00:19:09.580 --> 00:19:11.580
their a their API endpoints too.

00:19:11.890 --> 00:19:13.720
Mike Bifulco: that's something maybe
that we've glazed over a little bit

00:19:13.725 --> 00:19:17.000
here is that you, you have a pretty
interesting open source story as

00:19:17.000 --> 00:19:20.355
well that this is not a, you know,
fully private closed source product.

00:19:20.355 --> 00:19:23.205
So tell me a little bit about
that, the, the nature of open

00:19:23.205 --> 00:19:24.495
source and un key and sort of your

00:19:24.790 --> 00:19:28.540
James: Yeah, so un key is a
hundred percent open source.

00:19:28.540 --> 00:19:32.230
Every part of our platform is
there, including our landing pages.

00:19:32.320 --> 00:19:35.950
The API, there's no trade secrets
that are hidden somewhere.

00:19:36.350 --> 00:19:39.230
Everything is available for someone
to go and look at and learn from.

00:19:39.830 --> 00:19:44.510
The open source nature of
un Anki was from day one.

00:19:45.665 --> 00:19:48.875
We made the decision that if we were
gonna build something, we wanted to

00:19:48.875 --> 00:19:50.555
build it with open source in mind.

00:19:51.275 --> 00:19:56.255
And people are seeing more and more
people kind of build on open source,

00:19:56.255 --> 00:19:57.605
like build successful products.

00:19:57.605 --> 00:20:00.665
I mean, if you look@cow.com, they're
a really successful platform.

00:20:01.115 --> 00:20:04.325
And the only thing that isn't open source,
I think is just their marketing site.

00:20:04.835 --> 00:20:08.375
And we just believe that open
source makes better products.

00:20:09.350 --> 00:20:12.380
It makes it easier to do
security checks, right?

00:20:12.380 --> 00:20:14.630
Like if you're a big business, you
can just go and look through the

00:20:14.630 --> 00:20:17.090
source code and make sure we're
not doing anything nefarious or

00:20:17.090 --> 00:20:18.380
we're doing something dangerous.

00:20:18.890 --> 00:20:21.860
It makes it easier for people
to collaborate on an idea.

00:20:21.865 --> 00:20:26.210
So if they have an idea that like,
maybe this is a cool feature, they

00:20:26.210 --> 00:20:29.750
can create an issue and say like,
Hey, I'm thinking about this for Anki.

00:20:30.170 --> 00:20:31.160
What do you guys think?

00:20:31.160 --> 00:20:32.630
And then we have our community.

00:20:32.630 --> 00:20:33.860
We also have our team.

00:20:34.490 --> 00:20:39.350
And we can get to a point where an
idea may not be the best idea in the

00:20:39.350 --> 00:20:42.590
beginning, but by the time we've all
talked through iterations of it, we've

00:20:42.595 --> 00:20:47.640
come out with this next feature or an
extension of a feature that could really

00:20:47.640 --> 00:20:49.590
be useful for more than just one person.

00:20:50.130 --> 00:20:53.610
And we, we just found that we just
wanted to be as open as possible.

00:20:53.615 --> 00:20:59.780
So even internally as founders,
we are transparent with our team.

00:21:00.140 --> 00:21:01.790
So they know exactly what's happening.

00:21:01.790 --> 00:21:03.170
What are we doing?

00:21:03.710 --> 00:21:07.370
What kind of deals are in the
pipeline, what deals have fallen

00:21:07.370 --> 00:21:08.990
through or are successful?

00:21:09.320 --> 00:21:12.170
And then again, like things like
revenue and all that kind of stuff and

00:21:12.170 --> 00:21:13.220
how much money we have in the bank.

00:21:13.220 --> 00:21:14.990
All that stuff we're
completely open about.

00:21:15.440 --> 00:21:18.770
And it just makes for better overall
feeling every day knowing that

00:21:20.030 --> 00:21:23.840
nobody is in the dark and there's
no secrets that are being hidden.

00:21:24.350 --> 00:21:26.180
And we believe that
works for software too.

00:21:26.180 --> 00:21:27.080
Building that way.

00:21:27.545 --> 00:21:29.885
Makes it really easy for
someone to come and learn or, or

00:21:29.885 --> 00:21:31.325
contribute or whatever it might be.

00:21:32.155 --> 00:21:32.875
Mike Bifulco: Clearly it does.

00:21:32.875 --> 00:21:36.645
I think you've established as, as
a pretty impressive product and one

00:21:36.645 --> 00:21:38.545
that people are providing value to.

00:21:38.545 --> 00:21:41.845
Very quickly while we've been chatting,
I pulled up your GitHub repo, and I know

00:21:41.845 --> 00:21:45.755
this isn't exactly a direct litmus, but
it looks like you've currently got over

00:21:45.755 --> 00:21:50.015
1400 pull requests merged into the product
between, you know, now and its inception.

00:21:50.245 --> 00:21:53.025
Which is, you know, from any number
of, of contributors you know,

00:21:53.025 --> 00:21:54.435
between internally and externally.

00:21:54.685 --> 00:21:57.335
But one of the things I think
that comes along with that is you

00:21:57.335 --> 00:22:00.155
end up having to do almost like
crowdsourced product management too.

00:22:00.155 --> 00:22:03.420
And, and you touched on that a little
bit, but how, how do you balance,

00:22:03.425 --> 00:22:07.030
like taking feedback from open source
contributors versus paying customers

00:22:07.030 --> 00:22:09.075
versus what your team internally thinks

00:22:09.185 --> 00:22:13.535
James: Yeah, we spend a lot of time
talking about this just in general,

00:22:13.535 --> 00:22:17.225
so like being such a young company,
being less than a year old, it it.

00:22:17.705 --> 00:22:21.815
A lot of our direction comes internally
around we believe this is a feature

00:22:21.815 --> 00:22:25.475
that people want or need because
that's something we want or need.

00:22:25.565 --> 00:22:25.835
Right?

00:22:25.835 --> 00:22:27.665
Like it's one of those things
where you're like, I'm playing

00:22:27.665 --> 00:22:30.365
around with AI and it, wouldn't
it be cool if we had this feature?

00:22:30.995 --> 00:22:36.035
And, and so over the ti over the time
period, we've had people ask for feature

00:22:36.035 --> 00:22:40.505
requests and, and whether that's through
open source or being a paying customer.

00:22:40.895 --> 00:22:45.605
And it's just a fine balance of
deciding whether or not it's for the.

00:22:45.980 --> 00:22:50.030
Greater good of the product, or is it
a very niche thing that somebody needs?

00:22:50.450 --> 00:22:55.160
And if it's more niche, we try and pry
a bit more into what they're trying to

00:22:55.160 --> 00:22:58.820
achieve because it may be something we
already have on the roadmap, but it's

00:22:58.820 --> 00:23:03.320
like, you know, phrase in a different
way or, or what they're actually asking

00:23:03.320 --> 00:23:04.640
for is not what they really want.

00:23:05.150 --> 00:23:08.660
And we found over time that we, we've,
we've really got a fair balance there of

00:23:08.660 --> 00:23:10.580
like, Hey, this is a cool feature, but.

00:23:11.165 --> 00:23:14.015
Like, here's five different
edge cases where this probably

00:23:14.015 --> 00:23:14.945
wouldn't work properly.

00:23:15.395 --> 00:23:17.165
And like, what would you
think about this instead?

00:23:17.165 --> 00:23:19.235
And kind of talking to
the community in general.

00:23:19.625 --> 00:23:20.765
And that's been really good for us.

00:23:20.885 --> 00:23:24.275
I think it's a tough challenge and
I think anyone that has an open

00:23:24.275 --> 00:23:27.515
source project, it's just tough
to be like, we are not gonna build

00:23:27.515 --> 00:23:31.025
this, or we are gonna build this, but
it's gonna be six months from now.

00:23:31.025 --> 00:23:33.605
But if you wanna open a feature
request and like do it yourself,

00:23:33.605 --> 00:23:37.095
like here's how you can contribute,
and it, it's just tough.

00:23:37.185 --> 00:23:39.555
I think it's just one of those things,
you just gotta balance it the best

00:23:39.555 --> 00:23:43.365
you can and decide what's better for
the greater good of the company and,

00:23:43.365 --> 00:23:44.595
and the business side of things too.

00:23:45.455 --> 00:23:48.205
Mike Bifulco: By nature you have a
lot of constituents through opening

00:23:48.205 --> 00:23:52.285
the product up, and it's usually a
good thing to listen to feedback from,

00:23:52.285 --> 00:23:54.965
you know, customers and people who
maybe just want to use your product

00:23:54.965 --> 00:23:57.665
aspirationally, but are blocked by,
you know, something not existing.

00:23:58.245 --> 00:24:00.855
But definitely also certainly
have to balance this out as like

00:24:00.855 --> 00:24:03.375
it needs to run as a business and
be a functioning business too.

00:24:03.705 --> 00:24:04.755
There's, there's.

00:24:05.355 --> 00:24:07.725
Well, almost the curse of open source
is that when you're successful,

00:24:07.725 --> 00:24:10.545
you start to get a massive amount
of signal to noise problems.

00:24:10.865 --> 00:24:13.745
But the benefit of it too is when you
strike the balance, like your, your

00:24:13.745 --> 00:24:16.805
product also a little bit maintains
itself or maybe grows itself.

00:24:16.995 --> 00:24:20.255
And, and your team can, be more open
about that, you know, like, let's

00:24:20.255 --> 00:24:22.625
have a discussion about this feature
before we go and implement it.

00:24:22.625 --> 00:24:25.785
And it sounds like from your ethos
of keeping everything, you know, open

00:24:25.785 --> 00:24:29.415
with the team and, and being sort of
approaching the problem with open arms

00:24:29.575 --> 00:24:33.190
you can ask a few whys, like, okay, you
want this very niche feature, but I.

00:24:33.190 --> 00:24:36.155
Why, you know, and why to that and why
to that until you get to do something

00:24:36.155 --> 00:24:39.715
that maybe is a little more generic
or you know, I'm sure in, in some

00:24:39.715 --> 00:24:42.935
cases you're ending up saying no, but
you've had the discussion and hopefully

00:24:42.935 --> 00:24:45.755
publicly too, so everyone can kind of
learn from it and chime in as well.

00:24:46.455 --> 00:24:49.100
I'm, I'm I'm, I'm impressed how
quickly this has come together.

00:24:49.100 --> 00:24:52.570
Like it feels like you've got a a
timeline that makes no sense to me

00:24:52.570 --> 00:24:55.120
because it feels like you're traveling
through time but also a product

00:24:55.120 --> 00:24:57.080
that feels really, mature, right.

00:24:57.080 --> 00:25:00.290
Given that like there's a lot of polish
in what you've built and a lot of really

00:25:00.290 --> 00:25:03.380
thoughtful touches across your site,
across documentation, things like that.

00:25:03.690 --> 00:25:06.750
So I'm, I'm interested a little bit in
hearing about the developer experience of

00:25:06.750 --> 00:25:08.610
the product and from a couple of angles.

00:25:08.615 --> 00:25:11.600
So first why don't we start with,
tell me a little bit about like,

00:25:11.600 --> 00:25:12.980
the implementation side of this.

00:25:12.980 --> 00:25:17.210
I, I have a, a AI based product
and I want to use un key for

00:25:17.240 --> 00:25:18.650
you know, managing my API keys.

00:25:18.650 --> 00:25:19.550
How do I get started?

00:25:19.580 --> 00:25:23.720
James: Yeah, so it, we've tried to
make on key as easy as possible with

00:25:23.725 --> 00:25:25.610
the smallest amount of implementation.

00:25:26.000 --> 00:25:30.110
So if we just use TypeScript, 'cause
it's probably the easiest example because

00:25:30.110 --> 00:25:31.910
we have like official SDKs for that.

00:25:32.270 --> 00:25:35.990
Essentially the idea is you sign up
for an account through, through on key.

00:25:36.340 --> 00:25:38.950
And we give you an onboarding
experience depending on what you want.

00:25:38.950 --> 00:25:42.145
So if you are looking for API
keys, we, that's one onboarding.

00:25:42.220 --> 00:25:43.120
Onboarding experience.

00:25:43.120 --> 00:25:45.370
If you just want straight rate
limiting, we give you a different one.

00:25:45.880 --> 00:25:48.310
But when you go through that
experience, essentially what you get

00:25:48.310 --> 00:25:52.660
is something called a root key, which
is basically the keys to the kingdom.

00:25:52.660 --> 00:25:56.170
You can set it to be able to do
a bunch of different things, but

00:25:56.170 --> 00:25:59.620
the idea is that root key gives
you the ability to create a key.

00:26:00.220 --> 00:26:03.490
Or update a key or delete a
key, whichever one of those kind

00:26:03.490 --> 00:26:04.900
of operations that you need.

00:26:05.380 --> 00:26:09.400
So the idea would be that you have an API
endpoint somewhere that basically just

00:26:09.400 --> 00:26:13.270
says, you know, when a customer clicks
this button, create a key for them.

00:26:13.850 --> 00:26:19.050
And it's just a simple, a simple
SDK call to like un key client dot.

00:26:19.755 --> 00:26:24.295
Keys create and you give us some
sort of information based upon that.

00:26:24.295 --> 00:26:28.675
So it's just like our API ID and
then maybe you need a user id 'cause

00:26:28.675 --> 00:26:30.055
you wanna reference it to someone.

00:26:30.305 --> 00:26:33.725
We give you the ability to do that
and then we return you two things.

00:26:33.725 --> 00:26:35.795
The key itself and a key id.

00:26:35.850 --> 00:26:40.530
And the key is only ever returned one time
and we'll never be able to retrieve it.

00:26:40.800 --> 00:26:42.810
We'll never be able to
show it to you again.

00:26:42.810 --> 00:26:43.290
Basically.

00:26:43.290 --> 00:26:44.460
It's just a one time thing.

00:26:44.460 --> 00:26:47.040
'cause we, the way that we
store the keys securely.

00:26:47.535 --> 00:26:50.475
And in that point you give it to the
customer and the customer now has this

00:26:50.475 --> 00:26:54.615
key that whatever it might do to interact
with your system, then we just have

00:26:54.615 --> 00:26:56.535
another piece that's called verify key.

00:26:57.255 --> 00:26:59.205
And Verify key takes two pieces.

00:26:59.210 --> 00:27:03.645
It's the key itself and then the API
ID that you want to verify against.

00:27:04.075 --> 00:27:06.805
And then you just make a call to
that and we'll tell you whether

00:27:06.805 --> 00:27:08.185
or not they should have access.

00:27:08.185 --> 00:27:11.095
So if you've got rate limiting,
for example, and maybe

00:27:11.095 --> 00:27:14.515
someone's really hammering an
API endpoint and they've used.

00:27:14.950 --> 00:27:17.590
More than you've said that
they can use for rate limiting.

00:27:18.040 --> 00:27:22.150
We'll actually return back that you
sh basically it's a true or false

00:27:22.150 --> 00:27:24.640
statement and we'll just return false.

00:27:24.730 --> 00:27:26.650
And then at that point you can
handle it however you want.

00:27:26.650 --> 00:27:29.740
You can reject them, you can
tell 'em to calm down whatever

00:27:29.745 --> 00:27:31.420
you want to do through that.

00:27:31.690 --> 00:27:33.820
And that's basically
the way that it works.

00:27:34.180 --> 00:27:39.130
And then if the user is using something
like token, you know, usage based, and

00:27:39.130 --> 00:27:42.040
they're like, oh, hey, this person's
actually upgraded their account.

00:27:42.040 --> 00:27:43.180
I need to update the key.

00:27:43.510 --> 00:27:48.130
We have another call that you can update
key and then just give us whatever

00:27:48.130 --> 00:27:51.260
you need to update, whether that's
maybe their rate limits are higher

00:27:51.260 --> 00:27:54.410
now, plus they are, they, they get
more usage or whatever it might be.

00:27:54.800 --> 00:27:58.400
And the way that On Key's built, it's
built on a really simple rest, API.

00:27:58.580 --> 00:28:03.770
So if we don't have an SDK for it, the
rest API is really, really easy to use.

00:28:04.085 --> 00:28:05.935
We have an an open API spec.

00:28:05.935 --> 00:28:09.325
So if you want to use generator to
generate all the endpoints you can.

00:28:09.745 --> 00:28:11.935
And we've made it as easy
as possible to get started.

00:28:12.535 --> 00:28:18.355
In theory, if you wanted to do a next GS
app, for example, that had this a like an

00:28:18.355 --> 00:28:22.855
API endpoint, and then you need to verify
the key beforehand, you could probably

00:28:22.855 --> 00:28:25.555
do the entire UN key implementation in.

00:28:26.650 --> 00:28:29.860
Less than 20 lines of code,
including verifying your keys.

00:28:29.860 --> 00:28:31.360
It's very, very simple.

00:28:31.420 --> 00:28:35.020
We've made it as simple as possible
and it's really easy to get started.

00:28:37.825 --> 00:28:39.895
Mike Bifulco: I am sure many of our
listeners are thinking about the

00:28:39.895 --> 00:28:44.905
subtleties implied by everything you've
just said with a small amount of code.

00:28:44.905 --> 00:28:48.685
20 lines of code, you know, for next are
probably similar for other platforms.

00:28:48.735 --> 00:28:50.145
You've just described quite a bit of.

00:28:50.760 --> 00:28:53.310
Work that is not easy to achieve, right?

00:28:53.310 --> 00:28:56.430
It's like a very humble description of
a super cool product, securely issuing

00:28:56.430 --> 00:29:00.960
and reissuing keys and mapping them to
access rights and rate limiting and all

00:29:00.960 --> 00:29:04.680
that is a crazy amount of scope and like
a very cool thing to be able to just

00:29:04.680 --> 00:29:09.150
kind of you know, excuse the slightly
sarcastic, joke, but like NPM install

00:29:09.150 --> 00:29:10.890
and have, you know, your API managed.

00:29:10.890 --> 00:29:11.700
Like, that's wild.

00:29:12.090 --> 00:29:13.260
That's, that's such a cool thing.

00:29:13.660 --> 00:29:16.000
You also touched on something before
that I think is really interesting and

00:29:16.000 --> 00:29:19.300
maybe subtle if, if folks listening
haven't touched on this or needed to

00:29:19.305 --> 00:29:23.470
implement this for themselves, but
usage-based API usage when it comes to

00:29:23.530 --> 00:29:25.390
pricing is a really challenging problem.

00:29:25.390 --> 00:29:28.560
And for the reasons you were saying
before synchronous versus asynchronous

00:29:28.560 --> 00:29:29.760
is a really interesting challenge.

00:29:29.760 --> 00:29:33.120
So maybe I'll set the scene here and I'm
curious maybe you can describe like the

00:29:33.120 --> 00:29:34.680
problem space and why it's important.

00:29:34.680 --> 00:29:38.250
But again, let's say I'm building
an API product and you've,

00:29:38.310 --> 00:29:39.840
you've paid me for access to it.

00:29:39.840 --> 00:29:43.400
So you've given me, you know, 10
bucks a worth of API usage, and

00:29:43.405 --> 00:29:45.020
I have a usage based API call.

00:29:45.280 --> 00:29:47.570
There are a few things that
can happen as you're, you're.

00:29:47.600 --> 00:29:51.710
The, the value of your credits
with me drain having to do with

00:29:51.710 --> 00:29:55.770
like race conditions and depletion
and refunding and all of those

00:29:55.775 --> 00:29:56.850
sorts of things with my account.

00:29:56.855 --> 00:30:00.780
So how do you convey all of that
information to end users when you're

00:30:01.130 --> 00:30:05.480
James: Yeah, so it is very hard to do if
you're not using something like UN key.

00:30:05.600 --> 00:30:08.690
'cause usually it's like, oh, I
have to use my database to basically

00:30:08.690 --> 00:30:12.020
store a token number that then I
decrement and increment, and then

00:30:12.050 --> 00:30:15.710
I take the risk of like my DB being
slow and now they've burst through

00:30:15.710 --> 00:30:17.480
and now they're in negative numbers.

00:30:17.480 --> 00:30:18.620
Like how does that all kind of work?

00:30:19.160 --> 00:30:23.660
So with UN Key, we basically give
you the ability to, to put in a

00:30:23.660 --> 00:30:25.340
number, whatever that number may be.

00:30:25.820 --> 00:30:28.880
Let's say they pay for
a hundred uses for $10.

00:30:29.260 --> 00:30:33.670
At that point, you have a few options
with un key to decide how you want

00:30:33.670 --> 00:30:36.400
to handle the future of that key.

00:30:37.120 --> 00:30:41.830
So for example, let's say they decide,
oh, this product's terrible and I wanna

00:30:41.830 --> 00:30:43.480
refund, and you give them a refund.

00:30:43.870 --> 00:30:47.020
They technically still have access
to that key when you do the refund.

00:30:47.530 --> 00:30:50.650
And so what we can do is we
have a few different ways to

00:30:50.650 --> 00:30:52.330
kind of basically disable a key.

00:30:52.940 --> 00:30:54.410
So you can do it right
through the dashboard.

00:30:54.410 --> 00:30:57.830
So if you're still manually billing and
you're manually doing that, you can just

00:30:57.830 --> 00:31:03.200
go into the dashboard, find the key that's
linked to that user and disable it, and

00:31:03.200 --> 00:31:04.460
then they won't be able to use that.

00:31:05.150 --> 00:31:08.480
If you are doing automation where,
let's say they wanna refund and then

00:31:08.480 --> 00:31:10.430
you basically scrub their account.

00:31:11.330 --> 00:31:15.200
You can use either the delete
key, if you know for sure.

00:31:15.200 --> 00:31:18.140
They're never, ever gonna come
back permanently, delete the key.

00:31:18.140 --> 00:31:23.240
And now the, the key has become sort
of, you know, unusable or you can update

00:31:23.240 --> 00:31:24.650
their key and just say it's disabled.

00:31:24.650 --> 00:31:25.550
Maybe they'll come back.

00:31:26.150 --> 00:31:28.520
And then what we do to protect
you from things like race

00:31:28.520 --> 00:31:32.600
conditions and things like that
when you're using our key system.

00:31:33.245 --> 00:31:35.735
We don't let you do an
asynchronous request.

00:31:35.795 --> 00:31:38.165
We like, you have to wait
for us to actually respond.

00:31:38.405 --> 00:31:41.315
You can't just be like, I'm just gonna
assume everything's fine and continue on.

00:31:41.705 --> 00:31:46.325
And that protects you because
one, it basically stops your.

00:31:47.120 --> 00:31:49.850
Anything else being processed
until UN key responds.

00:31:50.390 --> 00:31:53.480
And because of the way that we work
behind the scenes, essentially what you

00:31:53.480 --> 00:31:55.190
get is the correct and valid number.

00:31:55.190 --> 00:31:56.420
Like we are heavily cashed.

00:31:56.930 --> 00:32:00.770
We know exactly what the number is at
the time when the user makes the request.

00:32:00.770 --> 00:32:04.400
So there's less of this worry of like,
I have to wait for my DB to respond.

00:32:04.405 --> 00:32:05.600
Oh, they've burst through.

00:32:06.260 --> 00:32:09.320
There's no way for them to actually
physically burst through that request.

00:32:09.890 --> 00:32:13.100
And then what you can do is like
once they deplete and get to zero.

00:32:13.640 --> 00:32:16.940
Maybe they wanna pay you $10 more and say
like, oh, I want another a hundred users.

00:32:16.940 --> 00:32:18.140
This is super cool product.

00:32:18.530 --> 00:32:19.790
Well, you can do the same thing.

00:32:19.790 --> 00:32:23.300
So you can either manually
just do an update call and say,

00:32:23.420 --> 00:32:26.060
give, update remaining, and
say, give me a hundred more.

00:32:26.780 --> 00:32:30.230
Or if it's like a monthly
subscription, we have the ability to

00:32:30.230 --> 00:32:32.090
refill automatically once a month.

00:32:32.570 --> 00:32:35.930
So every month, if they've billed,
you can just basically say, every

00:32:35.930 --> 00:32:38.180
month, just unie, handle this for me.

00:32:38.180 --> 00:32:39.050
I don't care about it.

00:32:39.470 --> 00:32:40.130
Just handle it.

00:32:40.535 --> 00:32:43.025
And that makes it really, really easy.

00:32:43.115 --> 00:32:49.595
And then the final piece to the puzzle
is in the very near future we, we will

00:32:49.595 --> 00:32:51.635
have web hooks for you to hook into.

00:32:53.015 --> 00:32:57.245
So we can tell you this user has done this
much usage if you're doing usage based

00:32:57.245 --> 00:33:03.125
billing on your side, and we can send that
to you in specific timeframes or usage

00:33:03.130 --> 00:33:05.045
base or however you wanna really do it.

00:33:05.555 --> 00:33:08.585
And so that you can bill
via like 30 day invoices.

00:33:08.590 --> 00:33:12.215
So like, let's say it's similar to us,
where once a month you get a bill from

00:33:12.215 --> 00:33:13.655
us and we tell you how much you owe us.

00:33:13.820 --> 00:33:17.120
You can now do that with UN Key and
not have to worry about implementing

00:33:17.120 --> 00:33:20.330
the entire thing on your stack
and use whatever billing partner

00:33:20.330 --> 00:33:23.360
you want, Stripe, paddle, lemon
squeezy, whatever it might be.

00:33:23.832 --> 00:33:25.247
Mike Bifulco: I suppose that
means somewhere under the covers

00:33:25.247 --> 00:33:26.567
you're probably using UN key to

00:33:26.622 --> 00:33:26.982
James: Oh yeah.

00:33:26.982 --> 00:33:28.002
Un key is built on un key.

00:33:28.032 --> 00:33:28.932
That is for sure.

00:33:28.982 --> 00:33:32.597
Yeah, we, we everything that
we do is powered by un key.

00:33:32.657 --> 00:33:35.987
It's always the classic trope of
like, you know, Clark is using

00:33:35.987 --> 00:33:37.187
Clark behind the scenes, right?

00:33:37.187 --> 00:33:39.647
Like, if you go to Clark's
dashboard, you have to log in

00:33:39.652 --> 00:33:40.967
with Clark to get into Clark.

00:33:41.297 --> 00:33:42.347
It's the same thing for us.

00:33:42.347 --> 00:33:43.247
So when you.

00:33:43.712 --> 00:33:47.192
Bill when you like create your
workspace and you create your API

00:33:47.192 --> 00:33:50.732
and you create that first root key,
that root key is then using UN key

00:33:50.732 --> 00:33:54.092
to actually build you a root key that
you then use for a specific account.

00:33:54.672 --> 00:33:55.812
It's very similar to that.

00:33:55.812 --> 00:33:58.572
And then like when you do a
verification, we verify that

00:33:58.577 --> 00:34:00.522
key against one of our own keys.

00:34:01.049 --> 00:34:04.249
Mike Bifulco: That creates,  a paradox
of its API keys all the way down,

00:34:04.249 --> 00:34:06.864
but that's, that's a great way to
build the product, making sure that

00:34:06.864 --> 00:34:08.064
you're close to it and using it.

00:34:08.884 --> 00:34:11.194
I I also wanted to talk a little
bit about maybe the other side

00:34:11.194 --> 00:34:12.964
of, of your product in DevX.

00:34:13.014 --> 00:34:16.654
And particularly with your background
in developer advocacy it feels

00:34:16.654 --> 00:34:19.084
like you've done a really good job
of, you know, making a splash and

00:34:19.084 --> 00:34:21.544
socializing this because of the
reputation you built for yourself.

00:34:21.544 --> 00:34:23.784
But I'm curious what what other I.

00:34:23.784 --> 00:34:28.104
Benefits your work in developer advocacy
has, has brought to engineering a product

00:34:28.104 --> 00:34:29.574
and building something that actually used.

00:34:29.574 --> 00:34:33.309
And maybe the additional caveat that
I'll add there is that I, having worked

00:34:33.309 --> 00:34:36.339
in developer experience for, for a while
myself, one of the things you hear,

00:34:36.344 --> 00:34:39.549
especially while interviewing is that
developer advocates aren't engineers.

00:34:39.549 --> 00:34:41.379
Like, don't build products,
can't build products.

00:34:41.689 --> 00:34:42.769
And, and I think that.

00:34:42.974 --> 00:34:46.484
Obviously is a, a trope and something
that has a lot of faults to it,

00:34:46.484 --> 00:34:48.794
but it's something that also just
doesn't get talked about, right?

00:34:48.794 --> 00:34:51.884
Like you have jumped from the world of
talking about building for developers

00:34:51.884 --> 00:34:54.374
to building for developers, and now
you've got a product that's out there.

00:34:54.379 --> 00:34:55.934
So yeah, tell me your secrets, man.

00:34:55.934 --> 00:34:56.474
I wanna hear it all.

00:34:56.669 --> 00:34:58.859
James: I, I think, yeah,
that classic trope of like.

00:34:59.849 --> 00:35:02.039
Dev advocacy never can build a product.

00:35:02.039 --> 00:35:06.329
Is is, is something that I
think was probably true when

00:35:06.329 --> 00:35:07.889
dev advocacy was new, right?

00:35:07.889 --> 00:35:11.789
Like it was just like more of
an educational kind of part

00:35:11.789 --> 00:35:13.319
than it was about anything else.

00:35:13.619 --> 00:35:18.599
And less about being involved in like
moving a product forward or pushing a

00:35:18.599 --> 00:35:23.259
product forward, or helping engineering
or whatever, helping customers, and, and

00:35:23.259 --> 00:35:28.119
because my development background was way
before I was dev advocacy, they gave me

00:35:28.119 --> 00:35:29.679
some of that skillset immediately, right?

00:35:29.679 --> 00:35:31.689
Like I could build a product
and don't have to worry.

00:35:32.199 --> 00:35:38.469
But I think having the background
in dev advocacy and being unafraid

00:35:38.589 --> 00:35:45.309
to be open is something that's
scary for a lot of founders, right?

00:35:45.309 --> 00:35:48.639
Like you see these cool products
like one time and then you never

00:35:48.639 --> 00:35:50.079
see or hear from them again.

00:35:50.544 --> 00:35:54.474
And then like two years later you find
out, oh, they, they shut the doors

00:35:54.474 --> 00:35:57.054
'cause they couldn't get another round
of funding or they just couldn't get

00:35:57.054 --> 00:35:58.404
traction in the space that they're in.

00:35:58.409 --> 00:36:01.884
And it's because you never see them
actually doing anything on either

00:36:01.884 --> 00:36:07.554
social media or blog posts or being on
podcasts because they're afraid that

00:36:07.644 --> 00:36:09.024
whatever they put out in the world.

00:36:10.149 --> 00:36:11.439
That's the be all and end all.

00:36:11.439 --> 00:36:15.789
Like it's gonna be cemented in history
and I can never go back on what I've

00:36:15.789 --> 00:36:19.989
said or I can never change my mind
or I can never improve the products

00:36:19.989 --> 00:36:21.129
because we've said this thing.

00:36:21.609 --> 00:36:25.539
We took the opposite approach was
just like, just even if we're in

00:36:25.539 --> 00:36:27.639
the middle of building sand, just
post it on social media and say

00:36:27.639 --> 00:36:28.779
like, Hey, this is coming soon.

00:36:28.779 --> 00:36:32.349
Or Hey, we built this and it's like
in alpha, like, love some feedback.

00:36:32.839 --> 00:36:36.319
Then doing podcasts and, and, and
blog posts about things that we

00:36:36.319 --> 00:36:38.649
have opinions on is a huge thing.

00:36:38.649 --> 00:36:42.669
'cause you know, the internet is
full of people's opinions and having

00:36:42.674 --> 00:36:44.169
our own as we've built this product.

00:36:44.229 --> 00:36:49.174
Like we have a blog post that's about you
UIDs and how like people will use them

00:36:49.174 --> 00:36:52.264
wrong and like, this is how you should
really try and use them and here's why.

00:36:52.264 --> 00:36:57.274
And that post is still one of our
biggest drivers to the product.

00:36:58.339 --> 00:37:03.289
And most of it comes from a place of
like, either, wow, this blog post is

00:37:03.289 --> 00:37:06.349
amazing, it's a really great read, and
now I wanna know more about products.

00:37:06.649 --> 00:37:09.739
Or, these guys have no idea
what they're talking about.

00:37:09.739 --> 00:37:10.939
They have no experience.

00:37:10.939 --> 00:37:14.449
Like, they're clearly wrong and like,
I have a really bad opinion about this.

00:37:14.449 --> 00:37:14.659
Right?

00:37:14.664 --> 00:37:19.129
So like you have these two
opposing opposite ideas and,

00:37:19.129 --> 00:37:20.299
and, and we just don't care.

00:37:20.299 --> 00:37:21.199
We're just like, cool.

00:37:21.204 --> 00:37:22.429
Thanks for coming and checking us out.

00:37:22.429 --> 00:37:22.669
Like.

00:37:23.449 --> 00:37:26.929
That's your opinion and you know,
you rightfully can have that opinion.

00:37:27.799 --> 00:37:31.879
And building all those things
together kind of really helps kind

00:37:31.879 --> 00:37:33.709
of cement the products as a whole.

00:37:34.129 --> 00:37:37.339
And then having this engineering
background and, and not being afraid

00:37:37.339 --> 00:37:40.159
to like be wrong about something.

00:37:40.639 --> 00:37:42.529
I am nowhere close.

00:37:42.529 --> 00:37:46.789
My ability is nowhere close to
my CTO's ability in engineering.

00:37:47.344 --> 00:37:50.614
So there's times where I'm
just like, ah, I just put this

00:37:50.614 --> 00:37:51.634
together and see what happens.

00:37:51.634 --> 00:37:53.344
And I push PR up and he is
like, what are you doing?

00:37:53.344 --> 00:37:54.424
Like, now this makes sense?

00:37:54.424 --> 00:37:57.064
And like, okay, well
let me go and try again.

00:37:57.064 --> 00:37:57.814
Like, kind of thing.

00:37:57.814 --> 00:38:00.874
And not being afraid to,
to, to learn as we go.

00:38:01.444 --> 00:38:04.084
Because a lot of the stuff that
we built, we had no idea what

00:38:04.084 --> 00:38:05.044
we were doing in the beginning.

00:38:05.434 --> 00:38:09.214
We were like, we think this is gonna
work, but we won't know until we try.

00:38:09.574 --> 00:38:11.674
And, and just being unafraid of that.

00:38:11.674 --> 00:38:13.924
And I think dev advocates are
the perfect people for that too.

00:38:15.124 --> 00:38:20.494
A lot of the time, you spend a lot of
time building content or education or

00:38:20.494 --> 00:38:24.904
talking to people or whatever it might
be, and there's a big chance that whatever

00:38:24.904 --> 00:38:28.804
you put out in the world, either people
aren't gonna like, they hate the, like

00:38:28.804 --> 00:38:35.134
they really love it, it's not very good,
or it miss them up completely and being

00:38:35.139 --> 00:38:38.914
able to like get back up and be like, oh
well, like we did our best with that one.

00:38:38.914 --> 00:38:41.659
Let's move on to another post or
another video, whatever it might be.

00:38:42.319 --> 00:38:45.169
That's the same I attitude that,
that you need to have, if you're

00:38:45.169 --> 00:38:48.619
gonna build a product, it's just
like, this might not work, but let's

00:38:48.619 --> 00:38:49.819
give it a shot and see what happens.

00:38:51.634 --> 00:38:54.544
Mike Bifulco: I love that, that's
like a masterclass in both developer

00:38:54.544 --> 00:38:58.234
advocacy and startup founder school,
you know, kind of slammed together.

00:38:58.894 --> 00:39:02.324
There is I feel like the, the, one
of the, the hidden superpowers of

00:39:02.324 --> 00:39:06.594
developer advocacy is learning to embrace
opening and working in the open and in

00:39:06.594 --> 00:39:09.124
public and, and benefiting from the.

00:39:09.439 --> 00:39:12.199
Internet's magical superpower of
every time you share something

00:39:12.199 --> 00:39:14.629
online, someone smarter comes along
and tells you why you're wrong.

00:39:14.949 --> 00:39:15.699
That's fantastic.

00:39:15.699 --> 00:39:18.069
Like as, as long as you look at
that as, Hey, I can learn from this.

00:39:18.074 --> 00:39:20.259
That's, that's a superpower,
that's a skill for sure.

00:39:20.809 --> 00:39:24.329
And I think a lot of founders, I, I
mentor a handful of startup founders

00:39:24.329 --> 00:39:26.609
and kind of give advice to folks who
are like early on in the journey.

00:39:26.614 --> 00:39:28.889
And one of the things that I
think people miss out on a lot.

00:39:28.894 --> 00:39:32.014
That a lot of building a product,
especially a developer focused product,

00:39:32.014 --> 00:39:35.344
is that you've gotta love building it and
rebuilding it and iterating and like every

00:39:35.344 --> 00:39:37.114
step along the way is part of the thing.

00:39:37.114 --> 00:39:38.434
It can't just be like, I did it once.

00:39:38.439 --> 00:39:38.914
It's done.

00:39:39.524 --> 00:39:40.304
It's never done.

00:39:40.364 --> 00:39:42.019
And that's, that's the fun part, right?

00:39:42.024 --> 00:39:43.219
You've gotta learn to love that too.

00:39:43.319 --> 00:39:45.329
It seems like you've married
the two together really well,

00:39:45.389 --> 00:39:46.889
and certainly your team has too.

00:39:46.959 --> 00:39:49.119
We actually haven't really talked
about your team much apart from

00:39:49.119 --> 00:39:50.319
yourself and your, your co-founder.

00:39:50.319 --> 00:39:51.979
But how big is the team right now?

00:39:51.979 --> 00:39:53.579
What, what are what's the scale you're at?

00:39:53.679 --> 00:39:57.009
James: five people total,
including myself and Andreas.

00:39:57.109 --> 00:40:01.609
We have two engineers and then one
design engineer who does both design

00:40:01.609 --> 00:40:03.559
and also a lot of front end work for us.

00:40:05.494 --> 00:40:05.764
Mike Bifulco: Yeah.

00:40:05.769 --> 00:40:06.184
Got it.

00:40:06.334 --> 00:40:06.604
Yeah.

00:40:07.034 --> 00:40:10.184
A small but mighty team building something
that's really, really pretty wild.

00:40:10.249 --> 00:40:11.429
Are you expanding at the moment?

00:40:11.449 --> 00:40:11.669
Are

00:40:11.684 --> 00:40:13.364
James: are not hiring right now.

00:40:13.424 --> 00:40:17.144
We just hired just recently,
actually April tonight,

00:40:17.149 --> 00:40:18.404
design engineer came on board.

00:40:18.404 --> 00:40:22.994
So we'll probably be hiring again core,
kind of close to the end of the year.

00:40:23.454 --> 00:40:28.314
We definitely don't wanna expand too far,
too early and then be like, well, well

00:40:28.314 --> 00:40:29.724
I don't know what you can do right now.

00:40:29.754 --> 00:40:33.804
'cause we're like, we're all doing these
tiny pieces, you know, or the, you know,

00:40:33.804 --> 00:40:37.464
the, the scary worry of being a founder
is like, what if we run out of money?

00:40:38.379 --> 00:40:39.279
I don't wanna have to tell you.

00:40:39.279 --> 00:40:41.799
Sorry, like you just got a job
with us now we have to let you go.

00:40:42.249 --> 00:40:44.889
But yeah, we'll definitely be
hiring kind of close to the end

00:40:44.894 --> 00:40:48.209
of the year again which is when
we started our first hire round.

00:40:48.209 --> 00:40:50.669
So probably like October, November,
we'll probably start hiring again.

00:40:52.589 --> 00:40:53.519
Mike Bifulco: Yeah, that's great.

00:40:53.549 --> 00:40:57.639
I will make sure by the way, to include
links to UN Key and to James and to

00:40:57.639 --> 00:41:00.489
all of the social, everythings in
the show notes, as well as actually

00:41:00.489 --> 00:41:02.019
the blog post you mentioned before.

00:41:02.209 --> 00:41:04.939
Before I let you go, I'm curious to hear
what's next, like, what are you thinking

00:41:04.939 --> 00:41:06.569
about, what's the next exciting feature

00:41:06.569 --> 00:41:08.969
James: Yeah, so we have a
couple of different things.

00:41:08.969 --> 00:41:13.709
So we're currently working on
a special project for AI users.

00:41:13.769 --> 00:41:16.769
Essentially the idea is
semantic caching for ai.

00:41:17.354 --> 00:41:21.794
So the idea is that we can save you
both money and also just speed and

00:41:21.794 --> 00:41:26.194
latency by using the same tech that
we use behind the scenes but give you

00:41:26.194 --> 00:41:30.634
the ability to, to really have some
really nice responses if it's something

00:41:30.639 --> 00:41:34.324
that's already been asked before and
you don't have to go and ask open AI the

00:41:34.324 --> 00:41:36.724
same thing or some variation of that.

00:41:37.194 --> 00:41:38.364
We're working on that right now.

00:41:38.364 --> 00:41:40.284
That should be released probably in June.

00:41:41.049 --> 00:41:42.009
If all goes to plan.

00:41:42.349 --> 00:41:47.869
And that will be our first real, like push
into kind of the gateway esque product.

00:41:48.269 --> 00:41:53.219
And then the really big thing in the
next probably 12 months will be gateways

00:41:53.219 --> 00:41:57.209
in some variation, but gateways that
developers can use instead of gateways

00:41:57.209 --> 00:41:58.949
that you need a whole DevOps team for.

00:41:59.309 --> 00:42:00.779
We wanna make it really easy.

00:42:00.779 --> 00:42:04.829
A few clicks, gateway, or here's an
API call and now I have a gateway.

00:42:05.249 --> 00:42:06.239
That's the idea.

00:42:06.244 --> 00:42:09.509
We're pushing towards the same
devex experience that you get with

00:42:09.509 --> 00:42:10.769
the rest of the UN key products.

00:42:11.294 --> 00:42:13.544
And then we just have a
few more things coming.

00:42:13.574 --> 00:42:17.084
Like we have a cash package coming
that's not really related to On Key,

00:42:17.084 --> 00:42:21.764
but is where we can help you do a lot of
like the heavy cash work in CloudFlare

00:42:21.764 --> 00:42:23.384
workers and things like that that we use.

00:42:23.384 --> 00:42:26.414
Now we're actually building that
out to be just a standalone package

00:42:26.419 --> 00:42:29.234
that you can use for whatever you
want and don't have to use on key.

00:42:29.714 --> 00:42:33.494
And then, yeah, it's just some generalized
improvements, more analytical data for

00:42:33.494 --> 00:42:35.624
you guys to ingest and play around with.

00:42:36.054 --> 00:42:39.864
Ingestible audit logs is coming so you
can actually push stuff to on key and

00:42:39.864 --> 00:42:41.964
then do something with it afterwards.

00:42:42.474 --> 00:42:46.074
Lots of things just to try and
help API development in general

00:42:46.494 --> 00:42:48.924
Mike Bifulco: There's never any shortage
of new features to build, especially

00:42:48.924 --> 00:42:49.959
when you've got an audience of

00:42:50.169 --> 00:42:50.559
James: Yep.

00:42:50.589 --> 00:42:53.889
There's never, there's never a time where
we're like, Hmm, what should we build now?

00:42:53.889 --> 00:42:57.549
We definitely know that there's things to
build and, and we're happy to build them.

00:42:58.000 --> 00:42:59.620
Mike Bifulco: james, that's
a really good spot to be in.

00:42:59.650 --> 00:43:01.120
I appreciate you coming to hang out.

00:43:01.150 --> 00:43:03.890
Last thing where's the best
place to find you online and

00:43:03.890 --> 00:43:04.850
what's the address to find UN

00:43:05.030 --> 00:43:06.830
James: best place to find
me is probably Twitter.

00:43:06.890 --> 00:43:08.090
It's where I spend most of my time.

00:43:08.090 --> 00:43:10.330
It's just James R.

00:43:10.330 --> 00:43:11.210
Perkins.

00:43:11.490 --> 00:43:12.360
You can find me there.

00:43:12.630 --> 00:43:15.240
And then for Un Key, you
can now find us@unkey.com.

00:43:15.310 --> 00:43:18.730
We just launched the new site
that you see today, which will be

00:43:18.730 --> 00:43:20.230
whatever anybody looks at right now.

00:43:20.420 --> 00:43:23.540
We launched that a couple of
weeks ago with un key.com domain.

00:43:23.919 --> 00:43:24.429
Mike Bifulco: it looks great.

00:43:24.429 --> 00:43:26.639
Congratulations on the
launch James Perkins.

00:43:26.699 --> 00:43:29.339
I am thrilled to be able to
talk to you and super excited

00:43:29.339 --> 00:43:30.269
to hear about your story.

00:43:30.299 --> 00:43:33.509
Please come back anytime when you've got
launches to chat through or things you

00:43:33.514 --> 00:43:36.234
wanna ask the community, or if you're
just interested in getting yelled at

00:43:36.329 --> 00:43:38.189
about open API specs, I can do that too.

00:43:38.559 --> 00:43:39.609
Thanks so much for joining me today.

00:43:39.609 --> 00:43:39.849
I really

00:43:39.909 --> 00:43:40.359
James: Thanks, Mike.

00:43:40.359 --> 00:43:41.079
Really appreciate you.

00:43:42.939 --> 00:43:43.209
Bye.

00:43:43.299 --> 00:43:43.539
Mike Bifulco: Soon.