0:00
I'm genuinely excited about what the future could be for a lot of people.
Search this video
0:03
The thing that I really love about Superbase is that like I see a lot of entrepreneurship because of the platform.
0:10
I certainly think that it'll be the case that everyone in the world with access to AI will become a builder of some sort.
0:17
Like you can build anything, you can customize it.
0:20
You want to make tweaks to some app, some UI, then you don't have to be beholden to to someone.
0:25
I'm pretty pumped about 2027 actually.
0:37
>> Welcome back to another episode of the Lightcone.
0:38
Today we're joined by Paul Copplestone, co-founder and CEO of Superbase, the open source Postgres backend that's become the default database inside tools like Cloud Code and Coda.
0:48
Superbase now has 13 million users and it's spinning up over a million databases a week.
0:53
Paul, welcome to the Lightcone. >> Thanks for having me.
0:58
>> So to start off, uh you know, famously YC gives you a t-shirt on the first day of YC that says make something people want, but increasingly all of us are realizing it's make something agents want.
1:07
And your company really exemplifies that.
1:13
You know, something like 70% of the new activity is from agents. Isn't that crazy? >> Yeah, it's wild. It's wild.
1:18
I think like this year especially what we've seen in terms of the numbers, the inflection is just a huge shift towards agents.
1:29
>> Just so we can understand just how much you guys have grown cuz it's kind of mind-boggling.
1:33
Yeah, like what are the numbers you care about and where were you like this time last year and where are you now?
1:38
>> I think this time last year, so yeah, we're 13 million sign-ups now.
1:40
Probably 12 months back we would have been around three perhaps.
1:48
This year like revenue will grow 4x.
1:52
We've got trying to think what we >> like a million databases being created per week at the moment. >> Yeah, over a million. Yeah, yeah, yeah.
1:59
>> What was it this time last year?
2:01
>> I think actually if databases under management now are approaching 50 million and this time last year it was 8 million, so it's just a huge huge inflection.
2:12
>> What's been driving that?
2:13
>> First, people are building with abandon, software engineers.
2:18
Second, I think that there are a lot more builders coming online.
2:21
So, what was traditionally someone with a software engineering background is now is now becoming possible for non-engineers to actually build things on top of Superbase.
2:34
>> So, this is a really big shift.
2:34
What have you guys actually done to facilitate or encourage this shift from, you know, obviously software engineers are going to keep choosing Superbase, but you know, how do you get the agents to come over in the first place?
2:50
>> Yeah, we largely have seen like three chapters in Superbase.
2:52
We started as a dashboard company, then we went to an API company, and now we're very much a code-first company, so we try to have the modalities that the agents really want to build with, which is code-first.
3:06
They really want to use CLIs most of the time.
3:10
The other thing is just being chosen as a default in the LLMs, which I think we were a huge beneficiary of our of our the timing of which we started to become a default choice for databases.
3:24
>> How much do you think being open source played a role in it, too?
3:26
Cuz the agents love open source things.
3:29
>> You know, it's hard to know the counterfactual, but I think it was critical.
3:31
I mean, everything that we do is open source and it seems to have been a a huge benefit to us and we do it in a very open sourcey way.
3:40
Like we try to support existing tools.
3:42
It's not just Superbase tools.
3:44
We we support like Postgres as a very famous tool for the Postgres ecosystem and we help to maintain that, so we kind of got sprawl across many communities.
3:57
>> I would guess that the agents actually really like open source because when something goes wrong, they can just look at the source. >> Yeah.
4:03
>> Yeah, I mean, I noticed the agents really like feeling powerful and they love data.
4:06
And uh there's nothing more frustrating than hitting a brick wall and then you don't know what's going on and you can't fix it.
4:15
>> I think it's going to be increasingly important as well because now with you know, security being so important, I think a lot of the say enterprises are going to want to inspect the source code to know that it's secure.
4:27
And if you've got closed source code, then you probably won't want to adopt them as a vendor.
4:34
>> Is developer even still sort of the the core user that you're going after or how you know, how do you think about it now in 2026?
4:42
>> Yeah, I think that the world where we're moving and at least what we're seeing this year is like uh kind of builders, builders are coming online and it's like a crazy amount of people coming online.
4:55
The crazy thing about this year is usually when you're uh like our top of funnel our sign-ups are accelerating and usually when this happens, you see a lot of the other numbers start to decline, activation, conversion, but actually
5:09
this year all of them are kind of going up into the right, which is a bit insane just because the models are getting so good at building and we're starting to see people who traditionally wouldn't have a software engineering background able to come and and build things. >> That's the distinction is like builder
5:25
>> That's the distinction is like builder as in they might not be actually software engineers so they might just be someone who needs to build a thing and they're just you know, popping open cloud code and then it turns out files only get you so far. >> Mhm. Yeah.
5:39
And in some ways like this category of people have all these spinned up ideas that they could never convince a software engineer to like help them build and now they don't have to convince anyone.
5:49
They've got all these ideas that they're churning out.
5:52
Software engineers still make up a huge portion, but the rate of the growth of the builder segment is is pretty pretty big.
6:00
Also like I don't know where the ceiling is on this one.
6:03
Like I I remember our early investors were saying PLG, product like growth, it's going to tap out at this revenue and you'll have to start moving into this segment of the market and there just appears to be no ceiling so far and I I can't see where it stops.
6:23
>> I mean, that was basically true like 2 years ago or 1 year ago, but definitely not true this year. >> Yeah.
6:29
>> I was just talking to someone actually last weekend if it's the builder category, it's like a fintech founder just exited his company with like over a billion dollars and he's always been sort of product adjacent like studying math at YC as an
6:41
undergrad and sort of like kind of could pull together some Ruby scripts, but they always need an engineer to like build the software and now it's side projects, he's just building his own stuff and he has all the knowledge from how to build a fintech company. So he
6:52
So he can actually build pretty sophisticated just like for his own personal finances like balance sheets and tracking software and knows how to like integrate in with banks and he's writing all the integrations from scratch and it's just like the kind of software that would never have been built even 2 years ago.
7:08
>> These are the perfect type of builder as well because like developers like me, I have very like developer focused ideas and things that I want to build, but then you got all these domain experts and they know exactly the niches of oh, this is an unsolved problem in my niche and so they're actually able now to like dig right into those niches without having to convince someone else to join them.
7:30
I think you guys were talking about this, weren't you in in YC like the profile shifting even from from who you're bringing into the cohort.
7:39
>> I think that if you look at the sort of era of what 2022-2025, there's sort of this real shift thinking like well, AI is coming and suddenly having software engineering as you know, core you you need a technical co-founder no matter what.
7:55
That was like a mega idea that you know, really came to the fore at YC during that time period.
8:02
It's always sort of true, but like sort of double down on that and then really in the last year we sort of said, "Actually, yeah, builders."
8:11
Like we're starting to see people who are able to like I mean the much harder thing to do is to know what to build.
8:18
You know, being able to build is something that anyone can sort of have on tap now.
8:22
And that's actually a really cool thing.
8:24
Like can you imagine all the things that never would have built exactly for what you said?
8:27
It's like, "Oh, we know that people would buy this.
8:31
We know that there's a problem here, but at the margins those people couldn't convince an engineer to work on [laughter] it."
8:39
>> And do you have some examples, Paul, of like apps that people have built on Supabase?
8:45
Maybe just for themselves that are the kinds of things that would have never been built before?
8:49
>> Uh well, one kind of cool example was at our conference.
8:51
We had the conference here and afterwards this guy from Brazil came up to me and he has built an entire taxi app uh from his phone.
9:03
And it's um kind of like a a little mini Uber for his local market.
9:07
And I just thought he's a taxi driver himself.
9:10
I don't actually know why he built it, but the fact that he could build it and he came up extremely grateful and that he could do this.
9:18
And also like with the type of energy he's he was like 50 years old or something like that, but he had the energy of a like teenager building suddenly, which I think is kind of cool because now it's kind of getting to that stage where I I think it's a little bit there's so much uncertainty around like what is the future of work going to look like, but in this category of builders there's that excitement of the future.
9:43
And that's really what I love about Supabase.
9:47
It's like something that people can come in and those who are uncertain now are discovering this skill set and these opportunities where previously they were just blue-collar workers, these type of profile.
9:59
>> All right, so you've been building some of your own personal software recently.
10:02
Can you talk about what you've been cooking up? >> growing.
10:03
Yeah, it's sort of like the end of one stop, but it's just growing out of um getting really addicted to open core.
10:10
Actually like maybe six months ago now I'm embarrassed that I said that I said that there was going to be no UI's and it was all just going to be like chat through my open core.
10:17
But it turns out actually and I also was really determined not to use a database for a long time.
10:22
I just wanted everything to be in markdown.
10:23
Um, but yeah it turns out actually you hit a point where like a database is useful and you do need UI.
10:29
And so I've just been building that over the last couple of weeks in particular and so it's like Um, I mean I call it a control tower but it's just like sort of every section of my life I find like I have like a UI to like triage all my emails so I don't need to read my inbox.
10:43
Um, finances, tracking like spending, health.
10:46
Like both I track my weights and my workouts and everything is all in like one place but I like the magic of it is sometimes it's a mind-boggling thought actually is like I think about like the finance section of like my one app for myself is better I think is at least feature parity to Mint or Monarch or all of these things but in some ways actually better because you can start doing really personalized context.
11:06
Like it can figure out what a transaction is by looking up in my like the name of my G brain out who that person is.
11:13
Oh, like that I know that's like and and and categorize it correctly.
11:17
And that was like a whole company like several startups just doing personal finance and I can just like build it for yourself and I don't need it to work for anyone else or like have anyone else's opinion on it.
11:27
It's just like kind of like my thing is like is kind of awesome.
11:31
>> We see a lot of that one like where it's finance and health basically the two like ones where you want your own data.
11:37
So we see a a lot of people doing that and syncing on the devices to to a single database is kind of a magic skill and you can like prompt it to like build these correlations across all of your devices.
11:50
>> that are really like again like if you just take the health example it's like yeah all of that data is in like my two base database but then it also has access to my calendar so it knows things.
11:57
Like it's like oh like your weight I know your weight went up recently but like you were traveling so that's okay.
12:03
Like you can just like get back on track um next week and it says like this context that's really valuable.
12:09
>> I also found that as I started to use the personal agents, like I'm getting a little bit paranoid that I'm putting all of like all of the um like routines and everything and the CRM is becoming like um boxed into one agent.
12:23
And so now I'm slowly extracting it out into one so that if I want to attach different agents on top, then I know that like I can use any any agent.
12:32
So the CRM is another really critical one.
12:36
>> Yeah, that's why you guys are so valuable is like actually like it's the the it's so like the store of record what's the the the database is actually thing that's valuable.
12:44
Like you don't you want to own your own database and then build all the applications or agents on top of it versus having that all in like someone else's database.
12:53
>> Which is a totally wild idea.
12:53
Like if you just think about the history of databases, used to be the case that like the world had only a relatively small number of very large databases run by like large companies.
13:04
And I remember like when Superbase got started, you kind of had this idea that they should be like really easy for everyone to like make a database.
13:11
And almost like didn't make sense at the time why so many people would want to do that cuz unless you can write code, what can you do with a database?
13:19
And there's not just not that many people who can actually like write code and build a personal CRM like that.
13:24
Like it's just like too much work for most people pre-AI.
13:28
>> Like another example actually where Superbase is really valuable for me is like the other section I have is just like a file upload.
13:32
Sounds very simple, but like any file I can send you the forward via email or just like dump it in this UI and then like my agent like figures out what that is and how it's relevant to my life and like what to do with it.
13:45
Um but that's all being stored on Superbase.
13:47
And so yeah, in general it's just like Superbase is actually going to end up having like all of the like data about my life in a single place.
13:55
And like I'm I would never I would never thought about wanting a personal database like a year ago cuz it wouldn't have made any sense.
14:01
But now I like that's actually like the most valuable thing.
14:04
>> Yeah, you have like an S3 compatible Superbase files thing and all my stuff is in that. >> Oh, really? Nice. Yeah.
14:11
>> It's default in G brain. >> [laughter] >> Great. Thank you.
14:15
>> Do you think this is the future, Paul, where like basically everyone in the world, not every developer, every person, will have a Supabase database that has stuff about their life in it, their health, their finances, their relationships? >> Yeah, we'd love that.
14:29
I mean, I I certainly think that it'll be the case that everyone in the world with access to AI will become a builder of some sort.
14:37
Like, you can build anything, you can customize it.
14:39
You want to make tweaks to some app, some UI, then you don't have to be beholden to to someone.
14:46
Of course, like, we think of ourselves as an index company.
14:48
We When we came into YC, we just focused on YC companies.
14:53
We wanted to win all YC customers.
14:55
And like, now, that was because we knew that we had to be there on day one when businesses were getting started.
15:02
The mission didn't change, just the aperture has like increased significantly.
15:07
Now, as more builders come online, we know that we need to service them, which is actually a whole different problem to solve, but kind of an exciting one.
15:17
>> Significantly meaning like 10 million X.
15:20
>> Yeah, like, so what, we launch now a million databases every single week, but I mean, if you do some basic arithmetic, let's say with ChatGPT, I think they said they've got 1.
15:31
2 billion weekly active users.
15:34
And let's say all of them want to launch something every month, that's 1.
15:38
2 billion databases a month.
15:42
And so, that's like the scale that we're moving towards, architectures that we need to have so that we can actually cater for for that scale, which is something that has never had to happen before on the database database realm.
15:56
>> Can you even do that with Postgres, or you're going to have to build your own database engine to scale to 1 billion new databases per week? >> I think, yeah.
16:02
Well, if we could negotiate better with AWS, then maybe we could, but it turns out that everyone wants computers at the moment.
16:12
And And actually, yeah, like, I don't know if you need like such a Ferrari for a lot of these workloads.
16:19
And we made an acquisition recently, Turso.
16:21
They've got a architecture that's compatible with Postgres.
16:26
And actually, it's compatible with SQLite as well.
16:29
I think SQLite's a phenomenal database.
16:31
And so, we'll provide this tier, which we call Superbase Spark, which is basically for for these getting started workloads.
16:38
The idea will be the same.
16:40
You get started with the same experience.
16:42
You can scale up to petabytes.
16:44
So, our tagline's kind of prototype to better petabytes.
16:47
And we as a company need to make sure that we can provide for everyone.
16:51
And if they do scale up and their business keeps growing, then we make sure that they have a great time.
16:59
>> Yeah, that's what I was curious about how you think about this actually.
17:01
Like the classic sort of software company, you start with, you know, maybe early-stage startups, like in a YC batch, and then you sort of have one eye towards the enterprise.
17:11
And I feel like especially if you're a database company, like pre-AI, the kind of futurism as well, like you want to be Oracle, so you got to get to the enterprise as quickly as you can because that's where all the money is.
17:20
And so, you start building out like enterprise features.
17:22
You're sort of leaning into SQLite is sort of going the opposite direction.
17:26
Like how do you how do you think about it?
17:28
Like are you sort of looking both ways? >> Yeah.
17:31
Yeah, we're having to do both, which is like incredibly difficult.
17:35
Basically, we've got two products that cater on the two ends.
17:37
So, Multigress will scale up to petabytes, and then Turso will scale down to like these prototypal and SQLite type workloads.
17:46
So, trying to do this at the rate of growth with like having to employ more people is just even with AI is becoming or has been a real challenge, but a fun one.
17:58
>> So, you ran a poll recently where people went from 10% of your engineers were writing 80% of their code with the coding agents, and then that number recently got up to 60% in a matter of 6 months.
18:13
Like how did that happen? What's happening?
18:16
Like, you know, where's this going from here?
18:19
>> So, we don't have an AI policy internally.
18:22
We just let people do whatever they whatever they want and we give them access to to whatever tools they they want to use.
18:30
And I think now is just that they're convinced that the models can do so much better better work and so much more.
18:38
So, the adoption has been crazy and yeah, the the things that they're building internally are not just five coded type stuff. They're pretty intense.
18:47
Um and as we're like shifting into this like AI coded realm, like just the amount of testing that we're doing and the tools that we're adopting for testing has been pretty useful to make sure that they actually know that the end result is going to be good.
19:04
>> Yeah, we're seeing that across YC the YC startups like uh Blacksmith Depot, Ubi Cloud, like they're all vertical cuz everyone's doing CI. >> Yeah.
19:13
>> And the number of tests that you have are just like through the roof. >> for like review.
19:18
>> So, that's pretty wild, honestly, to see.
19:19
Was it like a pretty like it's just the models are good enough now and like it's just people spend enough time where they're like, "Oh, actually, this is quite good."
19:26
>> And people need to be convinced.
19:27
Especially engineers, like I mean, they might not at the start of the year I've thought that it was very good.
19:34
And the models have gotten better, but also they're starting to see, "Oh, actually, you can achieve some great things with with these models."
19:42
And all the stuff with Navier-Stokes and all these stuff like convincing the market that actually, yeah, we can break new ground here.
19:50
So, I think that's the world that we're moving towards and now people are convinced that this is the way that it's going to be.
19:58
>> You've seen Superbase like through three eras.
20:00
First kind of like a dashboard company um built in 100 days during YC.
20:03
Then the API company and then now it's you know, sort of this agent, you know, make something agents want sort of moment.
20:12
Uh was there like one or two things like in each era that really jump out at you just like, "Oh, that was the thing that made us in that moment."
20:22
>> I think like those shifts happened.
20:22
So, the first one actually, yeah, I think you're saying like why would a database company exist when we came into YC?
20:32
>> It seemed like such a contrarian idea at the time, actually. >> Yeah. Yeah. Yeah.
20:35
I think like we saw how hard it was to use a database even for developers.
20:39
And so, that dashboard first was like, "Oh, let's build a UI that looks like Airtable on top of Postgres."
20:47
Because I actually loved Airtable as well.
20:49
I was like, "Wouldn't it be cool if that was just a Postgres database on the back end?"
20:55
So, um that one was just seeing that even software engineers struggled.
20:58
And then like when we moved to AI, I think we talked about this on the other podcast.
21:03
The AI API um shift was because we had someone integrating with us and they were like, "Oh, we want to launch lots of databases.
21:12
We need an API to do all of this."
21:15
And that was like 2021, maybe.
21:18
And it turns out that was exactly the right move for 2024 when the likes of Bolt and Lovable and all of these people started building on top of us.
21:28
Then this year, I just saw that actually no one's coming to the dashboard.
21:31
Like no one >> [laughter] >> No one visits dashboards anymore.
21:34
So, um how are agents going to build?
21:37
In this one, I just kind of put out a product memo to the team that said it has to be code first, get native.
21:45
Superbase just has to shift to to code first.
21:47
So, if it exists on the dashboard, it basically has to work in lockstep in code, infrastructure as code uh essentially.
21:56
And we re-architected a lot of the CLI and everything to work in sandboxes in code.
22:03
>> Were you guys maybe too far back, but were you inspired by Parse, another YC company? >> Yeah. Yeah.
22:07
Parse and Firebase, I I liked both of those companies.
22:09
And it's funny these waves, right?
22:13
Because they did the backend and Firebase acquired by Google Parse by Meta.
22:21
But in some ways I think they like blazed the trail for us to come along and actually have a legitimate database business because in 2014, it would have been ridiculous not to use RDS for your for your database.
22:35
Then they came along, came along, started moving to Atlas, and a lot of these database companies kind of showed that you don't need to just use one of the three hyperscalers.
22:47
You can actually have a legitimate database company.
22:49
And so that timing was crucial for us.
22:55
>> Yeah, people have sort of forgotten that, but it was like a really well-built product.
22:58
They launched like just when I was building iPhone apps for the first time, and it was like quite nice to switch to like a nice restful API as I was trying to deal with.
23:07
>> These shifts always happen with like inflection points, right?
23:09
So, at that point, there were two things that happened in the market.
23:13
Somehow, MongoDB convinced everyone that NoSQL was supposed to be like an amazing way to store your data.
23:21
And the second was mobile.
23:23
And so, you know, we're fortunate that we had a couple of these waves as well.
23:28
And now we're right in the thick of it.
23:30
And >> Yeah, I mean, this is what [clears throat] I was asking about, sort of like how you think about the enterprise versus early cuz I think I mean, if you go even further back, this is sort of like Heroku was the the first where it's like, "Hey, like just start with like the best developer experience and then scale up."
23:44
But like it is actually can be quite hard to like scale up with people.
23:47
And I think like, you know, Heroku sort of I don't think could quite bridge that gap to how do you keep people on you like as the apps get bigger and and need to be more performant, etc. , etc.
23:57
But like historically, every company's had to figure that out.
24:01
And like I mean, you guys are looking that way, but you might not have to.
24:03
Like honestly, if the the the the market for just owning like, I don't know, call it zero to 10, whatever, like keeps expanding at this rate, it's going to be huge.
24:14
>> Yeah, well, we won it all.
24:14
So >> [laughter] >> So, we might not have to, but we'll definitely do it.
24:19
And like kudos to Heroku.
24:22
I think they popularized Postgres.
24:25
But at the time, Postgres was pretty uh it was still pretty nascent and it still got some scaling um limitations.
24:33
And so, yeah, we've had to wrap Postgres in some tooling that will allow it to scale indefinitely, but >> I mean, I guess the better analogy for you guys is more like AWS was able to actually like get people early and like scale.
24:46
And so, do do Yeah, like what are the lessons maybe?
24:48
Like, how how do you think about making sure you can scale infinitely?
24:52
>> The lesson I think that they I heard a stat and was telling me Oh, I might get it wrong, so fact-check me, but something like 40% of AWS's revenue comes from like startups that started on them and then scaled up.
25:05
And like that's the category that we want.
25:08
You know, like we know that to convince people to migrate to from one database provider to another is near impossible.
25:16
And so, we just want to be there on day one, make sure that they have a great time, and then make sure that they actually don't want to leave.
25:24
>> business model as Stripe.
25:24
I mean, it's basically the best business model on Earth if you can get it.
25:27
Like, get them on day one and then just like scale with like the fastest-growing companies in the world infinitely.
25:33
>> And you just do that for a generation, and then you become a generational business. That's pretty much it.
25:36
Yeah, it's hard for us because what does day one look like?
25:40
That's rapidly sha- changing, so in the past, day one for me was always like YC customers.
25:45
And now, day one is becoming like Okay, everyone's a builder.
25:50
What are they going to use? What are the modalities?
25:54
What How are they going to choose their databases?
25:56
These are tricky questions.
25:59
>> YC's next batch is now taking applications. Got a startup in you? Apply at ycombinator. com/apply.
26:07
It's never too early, and filling out the app will level up your idea. Okay, back to the video.
26:13
>> It's kind of a different customer segment.
26:14
Like Like initially, when you started like there was not an individual market for databases.
26:18
Like the idea of a database company being a direct-to-consumer business would have just like sounded like a syntax error. >> Yes.
26:26
Um >> But now you actually have two segments.
26:29
You have the like early-stage companies that that that has this powerful stripe business model, but you're also like selling directly to consumers or to their agents perhaps. >> Yes, yes, yes.
26:39
>> And those use cases presumably will not scale the way startups well, but they might just like continue to use you for like for the rest of their lives because you're powering the app that like runs their personal finance software or your taxi cab company or something like that. >> Yeah.
26:53
And as their lives grow and they accumulate information, that is basically an index of our our own growth, you know?
27:00
So, they just store more.
27:02
People are collecting more data.
27:04
This kind of prosumer market is essentially a a good growth vector for us.
27:09
>> How do you think about the personal agent world in that through that perspective then if sort of coding agents want super base, it's very clear.
27:17
Like do you think about the next phase is being assuming we all have personal databases, they do need to do anything to make sure that it's easy for personal agents to talk to use that any different or is it basically the same >> thing?
27:29
>> Yeah, I'm very bullish now on personal agents after a week of my EA being away and me learning exactly what they can do.
27:38
And now I'm just kind of obsessed with the idea of building for personal agents.
27:42
And it's true that I I said to our company like we code first like we're building for humans that are doing code first, but actually we're doing it for agents.
27:52
Those humans pretty soon won't actually be interacting.
27:54
So, like the way I've been building is I'm using dots.
28:01
I just sit on a phone call with it all the time and I'm chatting to it and saying, "Oh, can you make these changes?"
28:06
And my my kind of heuristic to make sure I'm building or dog fooding correctly is that I just don't look at the code and I don't allow myself ever to check the architecture except when I want to check that it's actually building things correctly.
28:20
But when I'm making these changes, I just want to talk to it and see what it can change. So, >> One of us. One of us.
28:27
>> [laughter] >> It's crazy as well.
28:29
Like it's doing some phenomenal stuff that I just it it feels like something out of a sci-fi movie from a like 2 years ago, but now like I'm having so many of these moments that I'm just mind-blowing.
28:42
If you had shown someone this 6 months ago, they would have just thought it was impossible.
28:48
>> Yeah, you I was at your Superbase Select conference a couple of weeks ago, which is awesome conference by the way, and I had this like kind of crazy thought.
28:57
I was sitting there and you were talking about all these awesome new features that Superbase was putting out.
29:02
And I was like, you know, if I was building an app on Superbase, maybe I wouldn't even care to understand all these awesome features myself.
29:08
I want to like send my agent to Superbase Select to like listen to all the awesome new features and figure out how to integrate them into my codebase. >> Oh, that's wild.
29:17
A truly virtual conference. We should do that.
29:19
A conference just for agents.
29:23
>> A conference for [laughter] agents. >> They'll turn up live. >> Live.
29:25
They can [clears throat] like talk to each other, exchange tips on like, you know, Superbase live. Wow. >> You can bridge it.
29:31
You can sort of air drop them like the markdown files for everyone, but you have to be there in like the the audience to get it.
29:38
>> We'll call it the artifactory.
29:40
>> [laughter] >> Oh man, I quite like that.
29:43
>> We talked about before this, like there's just a bunch of things that you've been doing that like really make agents like you better.
29:49
Like error messages, you know, you know, what was that key insight?
29:53
And like are there a bunch of other things that you're doing that kind of obvious on the one hand, on the other hand like nobody's doing yet.
30:01
>> Yeah, so like the error messages, yeah, I was at a Dbt Labs in Boston night and I was surprised that this wasn't so obvious, but we really dug into our error messages so that you can take a use case like, oh, I want to build an application and generally like developer doing error messages are like 500 something basic and you just know there's a problem, but now you actually want the agents to like remedy themselves.
30:26
So inside the error messages, you are literally telling them how to fix this error or to go and read some docs to fix the error.
30:34
So a lot of it is just picking your use case and just trying to do these loops on improving your own error messages so that you can one shot basically anything that you want.
30:45
>> Yeah, that makes sense.
30:45
You basically, you know, if you're being used by an agent, the agent will encounter a error message.
30:51
In the past, a human would have to go Google that and do a bunch of stuff, but here you can just say, "Oh, like you're just, you know, out of inodes, so you should probably go do this."
31:02
>> Yeah, cuz there's like two stages to winning the agents.
31:04
The first is being picked by the model, and then the second is like if they get stuck, you don't want them to switch away, so guaranteed they'll get stuck at some point.
31:15
You just want to give them the tools to to remedy, so it's not actually that complicated.
31:22
They're smart enough now that they can figure out a lot of stuff, but you do have to re-engineer a lot of what previously was just for humans and developers for agents.
31:31
>> Do you test your project your product for agents?
31:33
>> Like do you have agents like try to use Supabase and then like report all the places where they had trouble? >> Yeah, yeah, yeah.
31:39
All the different models we've got on Evals website where we see which models are building the best, and we've got our own eval suite internally.
31:48
We eval as well which ones are best just with Postgres, so that's interesting for the industry and build skills around it so that they can adopt them and actually develop with Postgres.
31:58
So, yeah, it it's a lot of testing.
32:01
And in fact, pretty much now a lot of our engineering effort is going into like testing specific use cases rather than the building.
32:09
We want to think through how people are building and build suites around that.
32:16
>> Gary, when you built Gbrain, you built it on top of Supabase.
32:17
Can you talk about like how did you decide to build it on top of Supabase?
32:20
Well, how was it like for you to be a user?
32:24
>> Yeah, I guess I mean Gbrain was like a distillation of a bunch of stuff I wrote.
32:29
Like I first worked on Gary's list, which was like agentic.
32:31
It was like an agentic newsroom, and I had to build up like basically a research system for rag and for like policy and papers, and it would like read every newspaper article about a given topic, and then try to synthesize.
32:46
Um and then I took that and then distilled it into uh open-source retrieval for OpenClaw.
32:55
Cuz the idea was like, okay, I had it in Rails, and that was kind of like a Foxconn factory for agents.
32:59
It's like, I treated every LLM call as very expensive and incredibly dangerous.
33:06
And then when I saw OpenClaw, it was this, you know, it was kind of like Esselen.
33:10
It was just like a very different way for uh you know, you to work with AI, cuz then it's like, oh, the AI's smart.
33:17
Uh it's not trying to hurt you, and then you should just let it like do stuff, and you should just give it data and capabilities.
33:24
And so, I recognized a million tokens is actually an incredible working memory.
33:31
Like, most human beings only have like seven plus or minus two things that they can keep in their head, whereas like a million tokens is like basically uh like three Harry Potter books.
33:42
But then even that is like a little bit limiting for the agents.
33:46
Like, keeping the correct three Harry Potter books in your context at any given time is a real challenge.
33:50
So, it felt like there was this thing in between for a company brain or like my personal stuff.
33:57
It's like, you I have half a million markdown files on like every communication I've ever had.
34:01
And so, this thing really does have context on me and everything that I care about.
34:08
Uh but then at any given moment, like the agent, they might need like two pages or something.
34:13
It's it's a retrieval problem.
34:14
And so, uh at that point, you know, at many, I think it's like 30, 40 gigabytes, you need PG vector, you need Postgres, you know, you can do graph databases very easily in SQL.
34:27
And so, that's what G brain is.
34:30
It's like, you know, rag retrieval um plus like a a graph database that creates like structure out of unstructured data.
34:37
And so, it's like dynamic schemas, like a little bit like what I remember Palantir was back in the day. Yeah.
34:44
And then you know, the entire idea is that agents are much more powerful when there's sort of this intermediate thing where the agent can just say like this is what I'm looking for and it'll traverse the graph.
34:56
It'll do all of the you know, vector search and it'll come back and say like here here's a report and like load this into context.
35:04
And so that's what G brain is and then Superbase was just like very straightforward.
35:08
just like very straightforward. It's like I need I need hosted Postgres and I need it to be able to support like a 50 or 100 gig or 300 GB you know, database corpus really fast and it's been great like it you know, the auto scaling works
35:23
really really well and now the funniest thing is like with browser use like I use a side browser now for browser use and it's like oh yeah, like open clock can go into Superbase and you know, use the database or the new APIs you made and it just like managed it itself. It It can like self-manage.
35:39
>> Were you having to prompt it to like figure out the data structures like graphs or like rag or anything like that or >> I mean what's funny is like I I remember going into cloud code and just saying like use Exa and download download and diarize every paper you can find in AI research.
36:00
Today I could use like Alpha signal or something but it's like go and find every piece of research about rag and graph databases and like you know, text retrieval and then summarize it for like my use case which is like how do I help an agent get access to this stuff?
36:13
And then after it did that it's like oh okay, well here's a here's how we're going to do it.
36:21
>> Yeah, I was at a dinner the other night on like the future of databases and one idea was like databases essentially are like a retrieval mechanism for data and you know, you can put indexes so that they'll search across the data in certain formats so a graph or or rag and then one of them which was super interesting was just like putting an agent on a loop to create the perfect data structure for the search.
36:42
Like if you're searching this data set this many times and it's taking 10 seconds, then why don't you just put an agent on a loop to create a new type of index or like find the best index for returning that in less than a second.
36:58
>> dynamic retrieval is pretty clearly going to happen the second you have really really smart code gen. >> Yeah.
37:04
>> So, I mean for now, I mean I use it for open claw, so then I use my production instance and then the traces from that I extracted out like a eval data set and then I have a separate repo called G brain evals and it's got 40 different categories of like specific types of retrieval, retrieval efficiency, like cost efficiency, latency.
37:26
And then the cool thing about evals is then you can just tell the agent like loop, you know, just auto research and loop and anything that improves your stats on this eval like ship it into master on by >> default. >> Yeah.
37:42
And anything that you tried that didn't work, write a markdown file that, you know, explains why you think it didn't work and then file it away in G brain evals. I use Cappy.
37:49
There's a you know, Cappy has this concept of captains, which is kind of like similar to Grok bots bots.
37:55
And so you can just give it a context and so I have one that is always going that's like come up with new categories and I have another captain that's always going that's like go through all the categories in evals and auto research and every single day try to find a way to improve our scores on our own internal evals. >> Mhm.
38:16
>> And that's just going all the time.
38:16
It's a very very primitive version of RSI for like a particular use case, but I guess if you like go up one level of abstraction, you know, you could do that, you know, not for my use case, which is from for open claw or something.
38:32
Like it could just be for generically like anyone's retrieval use case.
38:36
Like the only thing that changes is like the use case and the traces and the data set.
38:42
>> You obviously know about evals and you can improve your software because you're like wrapping this framework around it.
38:48
Like do you think that in the future builders will have to actually know about these type of things or >> Maybe not.
38:53
I mean, honestly, I feel like we're so early that, you know, I'm just messing around.
38:57
And you know, I like doing it in open source.
39:00
And someone else, you know, I hope someone looks at that and says like, "Oh, I can apply that."
39:04
You know, like we're I think we're literally coming up with the primitives on how to use this stuff right now.
39:09
Yeah, I mean, I remember earlier in the year, you know, reading about Steve Yegge's uh factories and things like that and then not being able to totally figure it out.
39:18
And I was like, "Oh, no, no, I feel like now I've cobbled together something that works for me at least." >> Yeah.
39:25
>> Yeah, when we had Boris Turney here, um his vision of the future of coding was more like you just talk to Claude like a friend and you don't have to know about evals and all all this all this stuff.
39:35
And like Claude just like figures out how to build the thing that you have in your mind.
39:41
>> I've got this domain name openusd. dev.
39:45
And it's because there's actually a file format called openusd. dev.
39:47
And I collect domain names.
39:49
And then suddenly Stripe and Visa and everyone announced openusd. dev.
39:53
And I was like, "Oh, I better put this domain to use now."
39:55
But I never had time to to use it.
39:57
So, I was chatting to the dot and it's like developed this like developer side with the ecosystem and everything.
40:05
And I was just chatting to it on my computer.
40:08
And then I like as I was winding down my day, I called it on my phone like as I'm getting to bed, which sounds sus, but I'm >> [laughter] >> I promise I'm just >> in.
40:18
>> Just just coding with it.
40:18
And I was like saying, "Oh, I don't like the information architecture of how like the ecosystem links to the the use cases.
40:28
Can you make some suggestions?" And it did.
40:30
And I said, "Okay, yeah, implement them."
40:31
And then 20 seconds later it said, "Oh, yeah, okay, I've done it. Do you want to refresh?"
40:34
And I refreshed the site.
40:36
And it was really well written.
40:37
And everything was linking together.
40:39
And it's hooked up the SEO type stuff.
40:42
And so, I haven't done all the classic stuff that I'd have to do traditionally.
40:48
I've just been chatting to it and it really felt like one of those moments where I was I I sort of saw a glimpse of the future.
40:56
>> I mean, you can do that because you know what you want to build.
40:59
>> That's the thing, yeah.
40:59
So, like I obviously have a background in engineering.
41:03
So, I kind of know how to prompt it, but I'm trying to not say anything.
41:08
I'm trying not to like point it towards GitHub or anything like that and I'm trying to code like a like a normie or someone who next year so that I know it's basically so I can dog food Superbase and know that, "Oh, is it going to have a good time with Superbase in 1 year's time?"
41:27
>> Yeah, it's a funny for Boris to say like, "Oh, I I just wanted it to do it automatically."
41:30
And like certainly once it's into distribution, like literally the model has it, you know, in its weights. It can do it.
41:38
But until then, it needs like some markdown.
41:40
You just like a little like not even a lot of prompting.
41:45
Like very small amounts of prompting. It can just do it.
41:46
I mean, we're entering this very strange moment in society, I think, where like it sounds like RSI really is here and it's like going from like the 20% to 80% moment of like AI research is just happening in sort of these inside these loops inside, you know, Cloud Coder Codex or wherever it is.
42:07
And then simultaneous to that, like society doesn't really have enough people like you, Paul, who like know what to build and how to ask it.
42:18
And so, it's like unstoppable force meets immovable object right now.
42:23
Like the capabilities of the models are like going parabolic and then the number of people who know how to actually have an impact on society with it is like more or less constant.
42:36
>> Yeah, and want to be kind of excited by it.
42:39
I think that's the other thing.
42:39
I think a lot of people are getting paranoid.
42:42
But I'm genuinely excited about what the future could be for a lot of people.
42:48
A lot of my previous startups were focused on like blue-collar workers and like people who I was wrapping tech around a lot of people who just had to work a lot of their life, you know?
42:58
And I The thing that I really love about Superbase is that it's um like I see a lot of entrepreneurship um because of the platform.
43:09
And so I can see this future where actually there is going to be so much more entrepreneurship and it's actually quite a fulfilling lifestyle for a lot of people.
43:20
So I'm pretty pumped about 2027 actually as long as we can keep this cadence up and avoid a few few crazy events, then then it should be a fun ride for a lot of people.
43:32
>> We're seeing this moment where vertical SaaS founders actually are kind of struggling with raising series A's uh you know, when you're subscale like you know, 5 to 10 mil ARR even which like historically is a lot of ARR.
43:43
Like that's like a guaranteed series A even like 9 or 12 months ago.
43:48
And today it's like uh I don't know.
43:51
People are kind of like not really into it um for vertical like horizontal and AI investments like seems like it's uh totally green light, but like vertical SaaS people are really struggling.
44:03
But it's also sort of happening right at the moment where you can get to 10 to 15 mil you know, often 25, 30 mil, 50 mil with like 10 or 15 people.
44:14
And so at that point like you're very profitable at that point. >> Yeah, yeah, yeah.
44:19
With like if you got 15 people, 2 million ARR per head and with 50% margins, you're all making a million million a year.
44:26
I mean, that's an amazing outcome for for a lot of people. >> Yeah.
44:30
And simultaneous to that, we just do a lot of office hours with people who do like they got the brass ring and then they're bummed out that they can't raise a series A.
44:38
And so you know, many of my office hours there are just like you're probably going to look back on this as a blessing cuz you don't need the money.
44:47
Like time was you had to raise like a hundred million dollars to get to like 30 million a year in revenue cuz you just had to hire all these people, and now you don't have to do that. >> Yeah.
44:56
Yeah, there's a real thing in startups, like the badge.
44:58
I mean, it was the same for me, like to get funding at the start, like feel felt like, you know, I was achieving something great.
45:07
But actually, you know, to actually not fundraise now would in my mind be like, oh, that's achieving something great.
45:15
So, like, I'm a little bit envious of these companies that that are getting to that point.
45:20
>> Yeah, so I don't know.
45:20
I mean, we're it's a super changing world, but um your Superbase of all the companies has really been able to ride high through every single wave.
45:28
Um do you have any thoughts for people as they try to emulate what you've done?
45:34
>> One thing that helps me sleep well at night is that it's kind of the Lindy effect.
45:39
Databases have been around for 50 years.
45:41
I'm I think they'll be around for another 50 years, and this is one that at the end of AI, no matter what, I'm pretty certain they'll be databases.
45:49
So, parse from that whatever you will.
45:51
Like, uh you got to choose categories that are very durable, and if you're going to bet your entire life, which is basically what I I'm doing, you choose the category that you feel is worth investing in.
46:05
I think the other one is like, things are changing so fast, so we don't try to have all the answers as Superbase, but we just try to make sure that we're always adapting the fastest.
46:16
And, you know, for me, I've evaluated or like watched a lot of my favorite dev tools, um they kind of start with the developer focus, and then they always move up, and they become very corporate, and they kind of stagnate a lot, and they lose that that love.
46:34
And from our point of view, at least from my point of view, companies like Stripe, for example, they have this real like someone like a a founder who just cares about like almost focusing on what the new ways of building are.
46:51
And so, if you're like building for this next wave, you just always need to be one eye on the future of what is next, which is a very short timeline now.
47:01
Things are moving so fast, but um being super adaptable um and making sure you've got capacity within your team to shift very fast.
47:12
That's the thing that we're that we're focusing on for the next year.
47:15
>> I think that you've like maybe there's any specific things you've learned there?
47:17
Like cuz you've had you know, maybe you had the initial vibe coding inflection point and then the Opus 48 inflection point and just co-gen.
47:24
Like when the next sort of wave, hopefully next like many inflection point hit for you, but like are there things that you'll you'll do differently to be better prepared for it?
47:34
>> Well, first of all, like dog fooding is one of the most important things at least from our perspective.
47:39
So, I'm always trying these tools with ours to know, oh, where are the gaps?
47:44
There's no better feedback than you getting stuck on your own tooling.
47:48
Um and then having capacity.
47:51
So, we try to partner with with the the key players in the space.
47:54
And this ecosystem play has been really helpful because they give us feedback on what they're building.
47:59
So, that and we try to leave some capacity within the team, which is also very difficult, but um so that when they have ideas, we can we can give it a shot.
48:08
And not a lot of the bets actually win even when they seem like we're partnering together to do some new cool thing. We actually don't know.
48:17
They might sound cool and we try them out and they they they kind of flop.
48:21
But the ones that do work then end up meaning that we ride this awesome wave together.
48:28
>> That's a great note to end on.
48:28
Paul, thanks so much, man.
48:29
We'll see you guys next time.