WEBVTT

NOTE Sentence-level transcript of https://www.youtube.com/watch?v=HTzgC3FoYsI

NOTE One cue per sentence. Cue ids are the line anchors on /transcripts/HTzgC3FoYsI.html. A cue ends where the next begins, or 2 s after its last word.

s1
00:00:12.480 --> 00:00:14.480
Good afternoon everybody.

s2
00:00:14.480 --> 00:00:15.360
My name is Garrett.

s3
00:00:15.360 --> 00:00:22.640
I'm on the product team at WorkOS and you may see that the title of this slide this talk has slightly changed.

s4
00:00:22.640 --> 00:00:24.320
Uh, that's the bad news.

s5
00:00:24.320 --> 00:00:32.080
The good news is that the talk is better for it because the original idea I had for this talk two months ago uh is already sort of out of date

s6
00:00:32.080 --> 00:00:34.400
with how quickly things move.

s7
00:00:34.400 --> 00:00:39.360
So today we're going to talk about how do we enable anyone at your company to ship?

s8
00:00:39.360 --> 00:00:47.920
There are lots of people at your company that have great ideas of things that will solve problems inside your company but even with AI the technology still holds them back.

s9
00:00:47.920 --> 00:00:58.680
So I'm going to tell you the story of how we dealt with this problem, what we did about it and give you some advice if you're going to do it yourself or talk about what we're going to offer to help folks with this problem.

s10
00:00:59.520 --> 00:01:03.360
So this was about six eight months ago.

s11
00:01:03.360 --> 00:01:07.840
Uh, one of our account executives Perona she was about to go on maternity leave.

s12
00:01:07.840 --> 00:01:15.360
She's a incredible AE and she wanted to build something to help the rest of the sales team while she was on leave.

s13
00:01:15.360 --> 00:01:18.360
So she went and built something called Perona GPT.

s14
00:01:18.360 --> 00:01:26.800
Uh, it's basically a chatbot trained on her sales calls and all the stuff she knew about the product to help other people uh while she was out.

s15
00:01:26.800 --> 00:01:32.440
So she went, she built this at the time she used lovable, all the stuff she got it working great.

s16
00:01:32.440 --> 00:01:35.440
She shared it and said, "Hey, I have this tool that you can use while I'm out.

s17
00:01:35.440 --> 00:01:37.760
I hope it's helpful."

s18
00:01:38.360 --> 00:01:43.920
First thing our CEO Michael tries to use the tool and he gets this you don't have access.

s19
00:01:43.920 --> 00:01:49.160
He doesn't have a lovable account cuz he's not not used lovable uh and so he can't use it.

s20
00:01:49.160 --> 00:01:51.560
And so he's like, "Hey, how what can we do here?

s21
00:01:51.560 --> 00:01:53.480
How do we make sure everyone can use it?"

s22
00:01:53.480 --> 00:02:05.280
And so the solution was "Hey, two engineers on our applied AI team, can you go convert this into like an app that we can deploy and that we can give everyone access to?

s23
00:02:05.280 --> 00:02:15.600
So now we have account exec who comes up with a great idea, but in order to make that idea actually useful, we have to go get engineers to spend a bunch of time

s24
00:02:15.600 --> 00:02:20.680
recode it, you know, move it from lovable, deploy it, manage it, all this kind of stuff.

s25
00:02:20.680 --> 00:02:30.520
And this is really painful because really what should happen is she creates the app, deploys it, shares it, everyone gets access, and now people are are using it.

s26
00:02:31.000 --> 00:02:32.920
And so building things got cheap, right?

s27
00:02:32.920 --> 00:02:38.600
She was using lovable, that was kind of, you know, right around when like Opus 48 was coming out.

s28
00:02:38.600 --> 00:02:41.800
Now people are using Cloud Code, Codex and stuff in many cases.

s29
00:02:41.800 --> 00:02:46.720
And so it's not hard to build a thing, something that you can, you know, npm run dev.

s30
00:02:46.720 --> 00:02:48.440
It's pretty easy now.

s31
00:02:48.440 --> 00:02:54.320
But shipping it, making it available, even internally to your company, hasn't really gotten that much easier, right?

s32
00:02:54.320 --> 00:02:55.400
Where do you deploy this?

s33
00:02:55.400 --> 00:02:56.520
Where are you going to run this app?

s34
00:02:56.520 --> 00:02:58.200
How do you ensure it's secure, right?

s35
00:02:58.200 --> 00:03:05.120
How are people going to You want to I'll have your internal employees authenticate to it, but you don't want it to be publicly available.

s36
00:03:05.120 --> 00:03:12.239
And so, you know, for a less technical person, for a non-engineer, they're going to struggle with, you know, do I put it on Vercel?

s37
00:03:12.239 --> 00:03:16.239
Well, I don't have access to a Vercel account or a Cloudflare account because I'm not an engineer.

s38
00:03:16.239 --> 00:03:18.680
They might not know the details of how to do that.

s39
00:03:18.680 --> 00:03:25.680
Even for engineers who know how these tools work, they don't really want to have to go through this and do it from scratch every single time.

s40
00:03:25.680 --> 00:03:30.560
And then if you're deploying these things internally, you want them to have auth and security baked in.

s41
00:03:30.560 --> 00:03:36.880
You don't want people just, you know, shipping API keys to stuff that might get like checked into code bases or stuff like that.

s42
00:03:36.880 --> 00:03:37.560
And so what do you do?

s43
00:03:37.560 --> 00:03:40.760
You end up burning a bunch of engineering time to say, "Hey, this is important.

s44
00:03:40.760 --> 00:03:45.720
We need to go convert this to be some proper app deployment."

s45
00:03:47.280 --> 00:03:50.880
So the thing we needed at WorkOS was kind of two things.

s46
00:03:50.880 --> 00:03:56.560
One, the capability for everyone at the company to build a build and ship an application.

s47
00:03:56.560 --> 00:03:59.800
They shouldn't need to go ask infra for provisioning.

s48
00:03:59.800 --> 00:04:02.840
They shouldn't need to get like security approval for standard apps.

s49
00:04:02.840 --> 00:04:06.080
They should just build a build the thing and make it available.

s50
00:04:06.080 --> 00:04:07.760
And two, we want a distribution.

s51
00:04:07.760 --> 00:04:08.040
Right?

s52
00:04:08.040 --> 00:04:11.040
We want As soon as they ship it, they can link someone else to it.

s53
00:04:11.040 --> 00:04:19.120
That person can click the link and slack, open it up, and access the application without any red flags or any kind of red tape.

s54
00:04:19.200 --> 00:04:21.680
And so, we want to move fast.

s55
00:04:21.680 --> 00:04:22.440
We want to build quickly.

s56
00:04:22.440 --> 00:04:30.040
We have this applied AI team at WorkOS who's their kind of singular job is, how do we make AI more and more useful across the company?

s57
00:04:30.040 --> 00:04:39.000
Not just, you know, how do we move the software development process along, make engineers useful with AI, but how do we make everyone useful with AI?

s58
00:04:39.080 --> 00:04:40.520
Building, you know, building is cheap, right?

s59
00:04:40.520 --> 00:04:42.360
We can build a thing, no problem.

s60
00:04:42.360 --> 00:04:43.080
But how do we know it works?

s61
00:04:43.080 --> 00:04:45.640
We need to get the feedback around it.

s62
00:04:45.640 --> 00:04:52.560
Turns out we basically had a sort of a forcing function to gather feedback, which is we'd start doing these company-wide Cloud Days.

s63
00:04:52.560 --> 00:04:58.200
Basically, it's a single-day hackathon where everyone pairs up into teams and builds an app.

s64
00:04:58.200 --> 00:05:02.120
And typically, when we do this, we actually pair non-engineers with engineers.

s65
00:05:02.120 --> 00:05:04.760
And we actually have the non-engineers do the building.

s66
00:05:04.760 --> 00:05:06.560
They're the ones that have our hands on keyboard.

s67
00:05:06.560 --> 00:05:08.720
They're the ones building the application.

s68
00:05:08.720 --> 00:05:18.520
Uh while the engineer that's paired with them is there to consult, help them, you know, unblock them with any issues they find so they don't get stuck, kind of be a sounding board for, you know, how they can approach this.

s69
00:05:18.520 --> 00:05:27.800
But we have a ton of our, you know, marketing folks and sales folks that have all these really great ideas of apps that, you know, they've maybe struggled to bring to life.

s70
00:05:28.360 --> 00:05:30.160
So, we built two things.

s71
00:05:30.160 --> 00:05:32.240
The first thing is we built a CLI.

s72
00:05:32.240 --> 00:05:33.480
We call it wow.

s73
00:05:33.480 --> 00:05:40.120
Wow is the thing that helps you build and generate an app without needing to know any of the underlying details.

s74
00:05:40.120 --> 00:05:49.440
It basically is a toolkit that helps you set up Git, set up a repo, clone in an example application that you can use to start with for Cloud Coder Codex

s75
00:05:49.440 --> 00:05:51.760
uh to build the app you want to build.

s76
00:05:51.760 --> 00:05:55.080
And we distribute it to every single employee at the company through our MDM.

s77
00:05:55.080 --> 00:05:56.440
We just push it on your machine.

s78
00:05:56.440 --> 00:06:01.160
So, every employee day one has access to this tool.

s79
00:06:02.000 --> 00:06:05.160
The Well CLI lets you run things like wow app create.

s80
00:06:05.160 --> 00:06:10.160
What it does is that you name the app, it scans your machine and says, "Okay, do you have get installed?

s81
00:06:10.160 --> 00:06:12.880
Do you have you logged into GitHub?

s82
00:06:12.880 --> 00:06:15.000
Do you have Doppler which is your secrets management?"

s83
00:06:15.000 --> 00:06:26.480
Kind of does all this pre-configuration of your developer machine whether you're an engineer or not so that everything is kind of ready to go and you're not going to hit any snags along the way.

s84
00:06:26.960 --> 00:06:29.160
We also built a shared skills repository.

s85
00:06:29.160 --> 00:06:42.280
So, anyone at the company can if they built a skill that's useful, they can push that skill up and it's shared to everyone and then it's easy to fetch those skills, see what's available, and pull skills down to help you build things or or do certain workflows.

s86
00:06:44.360 --> 00:06:48.400
So, I'm going to do a quick demo to kind of show you a little bit of what this looks like.

s87
00:06:48.400 --> 00:06:54.560
Um So, here I'm in this folder and I want to create an app.

s88
00:06:54.560 --> 00:06:57.640
Let's do AIE demo.

s89
00:06:58.560 --> 00:07:01.120
And so, it basically runs through this whole flu- flow.

s90
00:07:01.120 --> 00:07:02.760
I've already obviously configured my machine.

s91
00:07:02.760 --> 00:07:04.560
It's not the first time I'm doing this.

s92
00:07:04.560 --> 00:07:10.120
So, it checks I have get, I have node, GitHub, Doppler, I'm signed in, everything.

s93
00:07:10.120 --> 00:07:15.240
And what it does actually creates a repo in our enterprise GitHub account.

s94
00:07:15.240 --> 00:07:18.440
Uh uses a kind of a template that we already have defined.

s95
00:07:18.440 --> 00:07:23.760
So, it starts out with basically a kind of blank Node.js app.

s96
00:07:23.880 --> 00:07:33.720
Um so, it does that, pushes everything, runs it, and then, you know, now we get some something that I can run internally or locally.

s97
00:07:34.320 --> 00:07:44.120
It does a little uh deploy step and then we get something available at localhost that I can pull up here.

s98
00:07:45.840 --> 00:07:48.440
And we have this internal app example.

s99
00:07:48.440 --> 00:07:55.240
If it's not obvious, we're running this on Cloudflare, um because it makes it really easy to quickly deploy um a node app.

s100
00:07:55.240 --> 00:07:56.480
So, this is great.

s101
00:07:56.480 --> 00:07:59.600
Single command, I now have this app running.

s102
00:07:59.600 --> 00:08:07.920
And then from that point on, you know, I can just, you know, pop into Claude and say, "Hey, I'm doing a demo for AIE.

s103
00:08:07.920 --> 00:08:15.840
What can we put in this app that would be cool?"

s104
00:08:21.480 --> 00:08:22.640
So, I'm going to let this go off.

s105
00:08:22.640 --> 00:08:24.640
I don't know, we're going to see what it does.

s106
00:08:24.640 --> 00:08:34.280
Um this is sort of just Claude being Claude, but um I want to walk through like a few parts of uh what we built in some examples of the things we built.

s107
00:08:34.280 --> 00:08:36.599
So, we have this uh internal registry.

s108
00:08:36.599 --> 00:08:41.200
So, anytime you push an app with Wow, uh we actually log it into the internal registry.

s109
00:08:41.200 --> 00:08:47.640
So, you can see we have 278 apps that have been pushed, uh 21 that were had a deployment done today.

s110
00:08:47.640 --> 00:08:52.400
Uh over the last week, we've had 3.3 million requests go through these applications.

s111
00:08:52.400 --> 00:08:59.920
So, these aren't just uh little dashboard tools, they're also APIs, Slack bots, and things that we created and use internally ourselves.

s112
00:08:59.920 --> 00:09:06.160
Um and then 60 of these are on sort of custom domains, so they have their own uh like branded um domain name.

s113
00:09:06.160 --> 00:09:15.280
A couple examples of things we built is um Connor on our product marketing team, we send these monthly newsletters that are like, "Hey, what's the latest in Work OS?"

s114
00:09:15.280 --> 00:09:22.960
Uh it's kind of a pain, we have to take updates that we have, put them into a format, and then we need to format them to send it both Slack and over email,

s115
00:09:22.960 --> 00:09:25.120
um which is pretty annoying.

s116
00:09:25.120 --> 00:09:29.839
And so, we built this uh I think my auth.

s117
00:09:29.839 --> 00:09:31.680
So, here's how these apps are protected, right?

s118
00:09:31.680 --> 00:09:34.760
I have to log in with my Okta account in order to access them.

s119
00:09:34.760 --> 00:09:41.200
So, if you go to uh any of these URLs, you'll see uh you won't be able to get to them.

s120
00:09:41.200 --> 00:09:44.800
So, here it basically pulls in all of our change logs.

s121
00:09:44.800 --> 00:09:45.800
You can curate that.

s122
00:09:45.800 --> 00:09:48.680
You can design what the Slack message is going to look like.

s123
00:09:48.680 --> 00:09:52.880
And so, it's a kind of singular place to design this experience.

s124
00:09:52.880 --> 00:09:55.480
I think that I built is we have a change log.

s125
00:09:55.480 --> 00:09:58.920
Changelog.workable.com/changelog is where we post all our updates.

s126
00:09:58.920 --> 00:10:02.360
And we do this through Webflow, which is like a CMS platform.

s127
00:10:02.360 --> 00:10:07.600
It's pretty It's pretty painful to actually like go in, design the change log post, and do all of this stuff.

s128
00:10:07.600 --> 00:10:11.920
And so, I built a tool that basically allows anyone at our company to draft these change logs.

s129
00:10:11.920 --> 00:10:13.560
And so, someone can come in.

s130
00:10:13.560 --> 00:10:15.560
Ooh.

s131
00:10:17.640 --> 00:10:20.480
I got to refresh my auth.

s132
00:10:21.960 --> 00:10:24.040
There we go.

s133
00:10:24.040 --> 00:10:29.960
Uh anyone can come in, kind of draft these change logs, and then it posts into Slack, so I can know, "Hey, there's a new change log someone's drafted up.

s134
00:10:29.960 --> 00:10:30.960
I can review it."

s135
00:10:30.960 --> 00:10:34.800
And then when it's ready, I can post it and then post it live.

s136
00:10:34.800 --> 00:10:38.000
So, this is what it the kind of tools that we're able to build.

s137
00:10:38.000 --> 00:10:48.160
Basically, anyone at our company can now self, you know, spin up Cloud Code, build the app that they want, and deploy it live, make it available to the entire company.

s138
00:10:48.200 --> 00:10:50.520
I'm going to I'm going to let that just sit in the background.

s139
00:10:50.520 --> 00:10:52.120
We don't need to see what that does.

s140
00:10:52.120 --> 00:10:55.839
Um but yeah.

s141
00:10:55.839 --> 00:10:57.040
So, that's that's the kind of idea.

s142
00:10:57.040 --> 00:11:00.720
Now we have uh tons of people at the company building these tools.

s143
00:11:00.720 --> 00:11:01.560
Uh nothing gets in the way.

s144
00:11:01.560 --> 00:11:03.480
They don't have to ask for, "Hey, can someone deploy this?

s145
00:11:03.480 --> 00:11:05.920
Hey, can someone provision some account for me?"

s146
00:11:05.920 --> 00:11:09.839
Uh everyone by default in the company can use this tool.

s147
00:11:09.839 --> 00:11:16.480
So, I want to talk a little bit about Atlas, which is the actual platform underneath this that uh powers this this this tool.

s148
00:11:16.480 --> 00:11:21.600
Wow is just sort of the CLI that people use to interface with it, but Atlas is actually the underlying infrastructure.

s149
00:11:21.600 --> 00:11:26.040
Basically, Atlas allows you to create, build, deploy, and share these applications.

s150
00:11:26.040 --> 00:11:32.600
There's sort of three principles when we're building Atlas that we wanted to maintain and and that provided a great experience.

s151
00:11:32.600 --> 00:11:34.760
One was we wanted the infra to be invisible.

s152
00:11:34.760 --> 00:11:37.760
No one should need to know where the deployment target is.

s153
00:11:37.760 --> 00:11:40.000
It happens to be that we're running on Cloudflare Workers.

s154
00:11:40.000 --> 00:11:43.120
If at some point we want to change that to Vercel or AWS, it shouldn't matter.

s155
00:11:43.120 --> 00:11:47.880
Should be transparent to anyone trying to build and deploy these applications.

s156
00:11:47.880 --> 00:11:49.320
Wanted to be secure by default, right?

s157
00:11:49.320 --> 00:11:52.320
We don't want to risk there's I can't show you all of the apps that we built.

s158
00:11:52.320 --> 00:11:55.800
Some of them have a lot of PII, they're customer tools, sales tools that we use.

s159
00:11:55.800 --> 00:11:59.600
So we don't want anyone just to be able to access these tools outside the company because they're very sensitive.

s160
00:11:59.600 --> 00:12:02.040
And then last is the discovery of discoverability.

s161
00:12:02.040 --> 00:12:07.920
Someone shares a link in Slack, anyone should be able to click that and be able to view that tool.

s162
00:12:08.720 --> 00:12:11.880
So today Ilist runs on Cloudflare's developer platform.

s163
00:12:11.880 --> 00:12:20.480
Every app, when you run that wild create step, provides compute, storage, uh with D1 databases, KV values, all the bits and pieces you need.

s164
00:12:20.480 --> 00:12:24.880
So you don't have to ask like, "Oh, well, if I need to like store persistent data, am I going to be able to do that?"

s165
00:12:24.880 --> 00:12:27.200
It's It's already part of the package.

s166
00:12:27.200 --> 00:12:31.520
Um and we automatically host all of these tools when you push them under workos.tools.

s167
00:12:31.520 --> 00:12:36.400
So we have this shared domain that whatever your app is called, you get that host name underneath workos.tools.

s168
00:12:36.400 --> 00:12:42.200
So you don't have to worry about where is the app going to be available, how does it get, you know, do people get access?

s169
00:12:44.520 --> 00:12:45.400
Secure by default.

s170
00:12:45.400 --> 00:12:50.000
So all of these apps are automatically protected by our Octa SSO account.

s171
00:12:50.000 --> 00:12:54.280
So you can't log in if you don't have access to our Octa account.

s172
00:12:54.280 --> 00:12:57.040
We've actually built for APIs and Slack bots.

s173
00:12:57.040 --> 00:13:00.800
We built a way to actually plug holes for a token-based authentication.

s174
00:13:00.800 --> 00:13:08.800
And so if that's something you need, you can build out uh you can kind of enable that and then get API access for some of these tools that we're using.

s175
00:13:08.800 --> 00:13:10.720
All the requests are logged and auditable.

s176
00:13:10.720 --> 00:13:12.520
So we have logs of all the traffic that's happening.

s177
00:13:12.520 --> 00:13:18.800
So if we think there was some sort of leak or um security issue, like we can go and detect what happened.

s178
00:13:18.800 --> 00:13:26.120
And then all the secrets, so if you need API access to any of our tools, internal tools, or third-party tools, that's all stored securely.

s179
00:13:26.120 --> 00:13:27.520
Uh we use Doppler in this case.

s180
00:13:27.520 --> 00:13:29.800
And so you don't really have to do secrets management.

s181
00:13:29.800 --> 00:13:35.920
You don't have to worry about did I, you know, push a secret into the Git repo that's now, you know, a problem.

s182
00:13:35.920 --> 00:13:38.640
It's all done securely.

s183
00:13:39.040 --> 00:13:41.680
And then last, we have the catalog for discovery.

s184
00:13:41.680 --> 00:13:43.400
Every app's discoverable.

s185
00:13:43.400 --> 00:13:44.680
Um no need to share.

s186
00:13:44.680 --> 00:13:49.400
You don't We don't need to have sharing support because you by default have access.

s187
00:13:50.280 --> 00:13:53.920
So, I think so far, you know, I showed you that catalog page which had a few hundred apps.

s188
00:13:53.920 --> 00:14:04.160
Obviously, not every single app is super important and sees the light of day, but we have about 60 apps that are been deployed, maintained, or getting used on a regular basis.

s189
00:14:04.160 --> 00:14:06.960
So, this isn't just like two tools people built that are useful.

s190
00:14:06.960 --> 00:14:10.560
It's actually becoming um a way in which things are being maintained.

s191
00:14:10.560 --> 00:14:16.080
We actually had someone build a tool where you take any arbitrary HTML, upload it, and it gives you a shared link.

s192
00:14:16.080 --> 00:14:22.440
So, it's basically like a mini hoster of like mocks or diagrams or things that you can easily share.

s193
00:14:22.440 --> 00:14:26.480
We're seeing over 3 million requests a week run run through all of these apps.

s194
00:14:26.480 --> 00:14:37.640
Um this is partially users using traffic, but it's also um one of our tools, Wallaby, is like a sales tool, and we actually built an APIs for that that allows us to access that data in other systems, in Slack.

s195
00:14:37.640 --> 00:14:42.720
And so, it's not just humans accessing this data, it's machines and agents as well.

s196
00:14:42.720 --> 00:14:49.360
We've completely eliminated the need for uh asking for help in deploying applications because nothing stops anyone anymore.

s197
00:14:49.360 --> 00:14:56.320
And I think like the most important metric is, you know, our our goal was enable non-engineers to build and deploy apps.

s198
00:14:56.320 --> 00:15:03.880
And out of our apps, out of these 60 apps, 37% of them have been built without any engineers in any of the commits.

s199
00:15:03.880 --> 00:15:08.680
So, they're totally built between that person and Claude without engineering involvement.

s200
00:15:08.680 --> 00:15:14.839
And that's sort of the marker of like a true success here that we've actually eliminated the need for, "Hey, you know, some engineer, can you migrate this tool?

s201
00:15:14.839 --> 00:15:20.160
Can you manage this tool on behalf of, you know, marketing or sales?"

s202
00:15:20.720 --> 00:15:21.880
So, So, more that we want to do here.

s203
00:15:21.880 --> 00:15:24.040
This is sort of initial version.

s204
00:15:24.040 --> 00:15:25.280
We want to add granular off.

s205
00:15:25.280 --> 00:15:29.240
Not every app should necessarily be opened by default to everyone in the company, obviously.

s206
00:15:29.240 --> 00:15:31.160
There's some sensitive data in some cases.

s207
00:15:31.160 --> 00:15:34.120
So, we want to add We already know who the user is when they're logging into the app.

s208
00:15:34.120 --> 00:15:40.440
So, we want to support doing kind of like group-based, role-based permissions for these apps easily.

s209
00:15:40.440 --> 00:15:41.800
We want to add more data integrations.

s210
00:15:41.800 --> 00:15:51.880
So, we kind of already have this capability aspect to to Wow and to Atlas where if I need access to our Snowflake data, for example, I don't need to go kind of think about API keys.

s211
00:15:51.880 --> 00:15:53.920
I can just say, "I want to add Snowflake."

s212
00:15:53.920 --> 00:15:57.600
And now the app has correctly maintained Snowflake access.

s213
00:15:57.600 --> 00:16:00.560
And then the other thing that we've we're building out is Slack integration.

s214
00:16:00.560 --> 00:16:11.560
So, a lot of these tools are great, but you really want them to be available inside Slack so that someone can just at the tool and get, you know, answer a question, get use out of it, or actually drive a workflow.

s215
00:16:11.560 --> 00:16:14.120
And so, we're building included Slack integration.

s216
00:16:14.120 --> 00:16:19.960
So, if someone deploys an app, they can also get the Slack app automatically installed.

s217
00:16:20.560 --> 00:16:25.880
So, for us, we're kind of experiencing ourselves a revolution in internal app development.

s218
00:16:25.880 --> 00:16:29.200
We've used other platforms to build certain tools.

s219
00:16:29.200 --> 00:16:31.200
We've always found them very cumbersome.

s220
00:16:31.200 --> 00:16:36.839
They basically still took engineers to build and maintain, and it sort of limited the tools that we could build.

s221
00:16:36.839 --> 00:16:43.360
For us, AI solved the build problem, but we needed more in order to make this a ubiquitous platform for our our our team.

s222
00:16:43.360 --> 00:16:48.520
Atlas provides these capabilities to enable anyone in our company to ship internal apps.

s223
00:16:48.520 --> 00:16:53.440
And if you're interested in having this kind of capability at your company, I'd love to talk to you about it.

s224
00:16:53.440 --> 00:16:55.560
Thank you.

s225
00:17:00.501 --> 00:17:02.501
[music]

s226
00:17:08.361 --> 00:17:10.361
[music]