Bridging research & product Leading @base44 product

Pinned Tweet
Following up on Karpathy's LotR world: why stop at books? I gave Opus 5 the Base44 repository. It built a world you can walk through. Every building is a module of the monorepo. Its height is the code inside it, its footprint is the file count, and how handsome it looks is how well that code is documented, tested and factored. The people are the contributors, walking the districts they actually commit to. Think what other worlds you can build from digital assets... Want to try it on your repo? Short instructions in the reply.
We're starting to leave the territory where you'd test an LLM by e.g. "create an svg of pelican on a bicycle". As one idea to generalize it, I was interested what Opus 5 would do if I gave it the first paragraph of the Lord of the Rings, a 1M token budget (~$10) and asked for three js render of it. Opus went off for ~2 hours and wrote 5500 lines of code that (procedurally) rendered the story. It's kind of janky but fun. But it's a bit mindboggling that the LLM has to place and orchestrate various polygon assets in (x,y,z) coordinates and write code that animates it all, and that it even does anything at all. I also like this kind of examples because no one in their right mind would ever spend the time to write something this custom but LLMs have all the stamina and patience in the world, so it's an example where we go from "no one would ever do this" to "sure, why not, it's ~free". There might be a lot more. But I'm excited about creating hyper custom worlds that you can imagine dropping players into, e.g. here to participate in the LoTR story as a spectator NPC, or one of the characters, or etc. Something like an ephemeral GTA of X on demand. Last thought is that the domain of worlds/games exposes a weakness in LLMs: they can't easily audit their work because they aren't able to efficiently and natively perceive videos or play games within them. Here, Opus 5 had to very slowly and painstakingly take screenshots at different points, and it messed up a few times and created a bunch of jank. An example of raw capability (multimodal, gameplay) that I think is still quite lacking.
7
3
39
274,451
Design used to live in files on one person's machine. Export, email, wait for feedback, save as final_v4. Then it moved to the browser, and the whole team started working in the same file. It wasn't just a better tool. It changed how teams work. Code never made that move. The product still lives on engineers' laptops, and everyone else sees it through screenshots and tickets. On a strong team, a preview environment after 20 minutes of CI. Building product should be iterative, collaborative and fast. That can only happen in the cloud. So today @base44 is launching Base Code: Connect a GitHub repo once, and Base Code gets your product running in the cloud. Setup is automatic and usually takes up to 10 minutes. PMs, designers, QA and engineers work on the same running product, from a browser. Describe a change and see it live. See what everyone is working on and jump into their branch. No screenshots, no waiting on CI. Engineers stay in full control. Every change ships as a PR: their review, their rules, their merge button. Check it out here: base44.com/base-code Want to try it? DM me and I'll send you a code for a free month.
Made with AI
4
2
21
81,713
Here is what I think the next product team will look like: Builder (dev + UX): the function in charge of actually building the product. A mix of dev and UX work, and I actually think that in 3-6 months, as models and harnesses improve, UX will have a slight edge here, since their work is much less verifiable than dev work. Product: highly focused on business impact. Understanding the market, competitors, seeing ahead of the curve, pricing. Weaving in a lot of user feedback to understand the business impact as well. No UX and fun product work. Grey, slightly boring, deep deep business work. Marketer: finding ways to get as many of the right people to the product. I think this will be (or maybe already is) the hardest function on the team, and I expect to see more and more high talent end up in this role. These personas should sit in the same room and constantly challenge each other. The marketer should influence the product as much as the product person, if not more. Onboarding and very quick value understanding are becoming crucial. Teams will reorganize around what stayed expensive.
2
2
25
1,676
Last week I opened my first PR to Base44's own codebase, from inside Base44. We connected our repo to the product and now build Base with Base. We'll probably call it Base Code, The name isn't final. And it's not just for us. Connect any GitHub repo, and everyone on the team, on every project, can work on it through Base: - Open the codebase - Make any change - Ship a PR No local setup. A full working environment usually takes up to 10 minutes. We are talking the whole stack, database and everything. It's time to truly unlock product, UX, and whoever else wants to build, From wherever they want to build. Link below if you want to try out on your own.
4
2
25
2,763
Yoav Orlev retweeted
We just blew past $200M ARR at @Base44 5 months after hitting $100M. We've released Base 1 in between. i'm proud of the healthy business we're building, being the only platform to own its entire stack (backend, models, etc) - which also allows us to move fast and be creative. All credits go to a very special team that i'm having so much fun working with
89
51
673
686,476
Yoav Orlev retweeted
We launched our second product - Superagent, 4 months ago. It’s been growing fastttt Here’s Superagent by the numbers: - 850,000 agents built - 285,000 agents have an active automation. making the agent work around the clock - 265,000 agents are also managing a @Base44 app - 170,000 agents are helping people manage their personal lives My fav use cases: • An avocado farm that runs its entire operations through agents and automations • ⁠A family of 6 that uses the superagent as the household cfo, logging expenses over WhatsApp and working out who owes whom • A sports scientist built force-velocity profiles for thirty athletes off GPS data • An insurance company built a prospecting agent and then started wondering whether to sell it as a product.
8
12
87
8,113
Yoav Orlev retweeted
Until now, onboarding to Superagent was: here's a chat. Good luck. We realized one of the hardest product problems isn't building an agent that can do things - it's explaining to you what it can do for you. So we rebuilt onboarding from scratch (honestly, we built one for the first time). And after a few hours of brainstorming with @OrlevYoav, we decided that instead of building just screens, we'd hand onboarding to the user's Superagent itself. Connect your email and calendar, and it gets to know you - then comes back with routines built around your week. Unanswered threads become draft replies. A pile of newsletters becomes one summary. No blank screen with a blinking cursor. No guessing. Your agent shows up already knowing you. And this is just the beginning, explaining what an agent can do for you is an infinite canvas, and cracking it will be some of the most important work we do.
3
9
587
The scariest sentence in a company IT review: "our HR specialist built this." @Base44 's most obvious builders are people who just decide to build something. But plenty of them wanted to build for the company they work at, and that was never a natural thing for a big company to allow. Trusting that your accountant is going to build the tool everyone else has to use. 6 months ago, Felix Koblenz and Moran Gutman set out to fix that: make Base44 the best platform for organizations and enterprises, without giving up what we already are, the best place where anyone with an idea becomes a builder. Since then, the team shipped: Security Center A single place to see the security posture of every app in your workspace. Automated scans, findings, and fixes, so security stops being a blocker for shipping. Connector Governance Admins now control which connectors and integrations are available across the organization. Teams move fast, IT stays in control. Groups Manage access by team instead of user by user. Assign apps, permissions, and resources to groups and stop maintaining permission manually. SSO Sign-Up Sign in with your organization's identity provider from day one. No new passwords, no shadow accounts, full compliance with your existing auth stack. Version History Every change to your data is tracked and reversible. Someone broke something? Roll back in one click. The accountant can build the tool. IT can sleep at night. Those are no longer opposites. And the team is just warming up..
1
4
27
1,822
Following up on Karpathy's LotR world: why stop at books? I gave Opus 5 the Base44 repository. It built a world you can walk through. Every building is a module of the monorepo. Its height is the code inside it, its footprint is the file count, and how handsome it looks is how well that code is documented, tested and factored. The people are the contributors, walking the districts they actually commit to. Think what other worlds you can build from digital assets... Want to try it on your repo? Short instructions in the reply.
We're starting to leave the territory where you'd test an LLM by e.g. "create an svg of pelican on a bicycle". As one idea to generalize it, I was interested what Opus 5 would do if I gave it the first paragraph of the Lord of the Rings, a 1M token budget (~$10) and asked for three js render of it. Opus went off for ~2 hours and wrote 5500 lines of code that (procedurally) rendered the story. It's kind of janky but fun. But it's a bit mindboggling that the LLM has to place and orchestrate various polygon assets in (x,y,z) coordinates and write code that animates it all, and that it even does anything at all. I also like this kind of examples because no one in their right mind would ever spend the time to write something this custom but LLMs have all the stamina and patience in the world, so it's an example where we go from "no one would ever do this" to "sure, why not, it's ~free". There might be a lot more. But I'm excited about creating hyper custom worlds that you can imagine dropping players into, e.g. here to participate in the LoTR story as a spectator NPC, or one of the characters, or etc. Something like an ephemeral GTA of X on demand. Last thought is that the domain of worlds/games exposes a weakness in LLMs: they can't easily audit their work because they aren't able to efficiently and natively perceive videos or play games within them. Here, Opus 5 had to very slowly and painstakingly take screenshots at different points, and it messed up a few times and created a bunch of jank. An example of raw capability (multimodal, gameplay) that I think is still quite lacking.
7
3
39
274,451
Build a 3D city in three.js that IS this repository. Take your time, be creative. First mine the repo into JSON: one pass over `git log --no-merges --name-only` plus a file census. Per directory — lines, files, commits, commits in the last 30 days, top authors. Per person — commits, first/last activity, what they touch. Then build the city from that data. Every visual property must be a measurement. Nothing decorative. Zone it into three areas with genuinely different architecture. Here's the one rule that matters: DON'T map size to height everywhere. frontend/UI → SUBURBS. A module is an estate of detached houses. Lines buy LAND, files buy HOUSES. Two storeys, never more. backend/core → DOWNTOWN. A module is a setback tower. Lines buy HEIGHT. tests/infra → THE WORKS. A module is a hangar with a barrel-vault roof. Lines make it LONGER, not taller. Make height mean lines-of-code everywhere and all three zones look like the same city. Spending the measure in a different dimension per zone is the whole trick. Score every module on how well it's built — has its own docs, test ratio, average file size, largest file — and let that decide how handsome the building is, in its zone's vernacular: raw concrete through to landmark. Don't soften it. The most important module in the repo scoring worst and getting a concrete slab is the most interesting thing the city will ever tell anyone. The people are the contributors. Sized by commit count, coloured by the area they work in, walking routes through the code they've actually touched. Anyone quiet for a month stands as a bronze statue instead of pretending to still be here. Bots fly. Night, dusk and day. Street lamps that actually light the road. Hover for the numbers, click to inspect, a mode with no UI at all, and a tour that flies the whole thing. No build step and no new dependencies: plain ES modules, three.js from a CDN import map. Then screenshot it and iterate on what you see — most of the design only becomes obvious once it's rendered.
6
289
Our users never asked for branches. They don't know the word. But I heard the need all the time: "I'm in the middle of building a big feature and I need to fix something small in my live app" "I want to work on a couple of features at the same time" "I have a big idea but I don't want to risk what already works" Same need, different words. So we shipped Branches. Make a copy of your app, experiment, merge it back when you're happy. If it doesn't work out, throw it away. You could always revert in @Base44 . Now you can also explore. This is the part I love most about building Base44: taking concepts engineers refined over decades and handing them to people who never heard of them. No new vocabulary to learn. It just works the way you'd expect. Go build. You won't break anything.
2
3
31
1,455
We're building something new at @Base44 , and we're looking for early testers. Until now, Base44 was for building apps from scratch. We're changing that: soon you'll be able to import an existing project straight from GitHub and keep building it in Base44. How it works: Connect your GitHub repo, and our agent explores it and figures out how to run it It spins up a live dev environment with a working preview, usually in minutes From there you edit with AI like any Base44 app: describe a change, see it live No local setup, no docker-compose debugging, no "works on my machine". This is especially useful if you're a PM or designer who wants to work on a real codebase without setting up a dev environment. We're opening this up to a small group of early users. If you have a project you'd want to try it with, sign up here: import-project.base44.app Would love to hear what kinds of projects you'd bring.
2
183
Yoav Orlev retweeted
Announcing Base 1’s benchmarks: After rigorous testing in production, attached below Base 1 results for building beautiful, functional and complex web apps inside @Base44. we released Base 1, our own model, a few weeks ago. we've been measuring it since. For app building, there are no standard benchmarks. We A/B test in production with millions of builders, who we believe provide the best benchmark for measuring real value across real-world use cases. Base 1 came close to Fable, while being 4.5x cheaper. Base 1 has the lowest frustration of anything we've tested. below Sonnet 5, below Opus 4.8, below Fable 5. Fable 5 still edges it on success rate, 76.4% to 74.9%. i'll post the full benchmarks in the comments
26
26
327
449,164
We just shipped data version history in @Base44 , and it's a bigger deal than it sounds. Most platforms give you a daily backup, or a 7-day snapshot if you're lucky. We store every single change to your app's data. Every create, update, and delete, captured the moment it happens. Deleted 500 records by accident? Broken automation corrupted your data? Bad impor? Browse your data at any point in time, and restore it. Not "restore to last night," restore to the exact moment before things went wrong. The best infrastructure is the kind you never notice. You build, you break things, you click restore, you move on. Available now in Base for all Elite tier and above.
1
1
10
767
Yoav Orlev retweeted
TLDR: I’ve started a small fund from my Base44 money that’s focused on cancer research and breakthrough therapies. I’ve invested in 7 incredible companies in the past 4 months and plan to do more as my liquidity allows. Listing my investment thesis below I welcome anyone like me who has been blessed financially to join me and find ways to finally manage or even end this disease. Longer - I honestly believe cancer is humanity's worst enemy. ~40% will be diagnosed with it, and out of which a ~third won’t make it. And numbers are currently not getting dramatically better. For many it might sound like a statistic But for some of us who have been there ourselves or had to go through it with a person we love, it’s one of the worst things you can imagine. I had to go through it with my mom - who passed away 4 months ago and whom I miss and think about every single day since. This field needs a dramatic push. The current wave of technology and AI is doing a lot of good in the world, But cancer therapy is one of those things that are not moving nearly fast enough. And there’s no good reason for that - AI is creating so much opportunity right now. Here's my thesis on how things will play out: For drug development, the bottleneck will shift to 1. Manufacturing 2. Real world testing "In silico" is going to accelerate incredibly fast. AI is identifying new target proteins and designing new molecules, drastically shortening timelines. AI will create an abundance / inflation of ideas. It will help design molecules faster than anything historically possible. This is already happening. Play with Claude Science or Codex and you'll be surprised at how far you can get with just a few prompts. We need a better way to *manufacture and test* the 1000s of ideas coming from AI models spitting out potential drug candidates 1. Manufacturing: i.e. how fast can we synthesize a potential drug Not too far into the future, companies with manufacturing excellence will win over companies with the smartest scientists. Being able to synthesize a drug candidate fast - together with efficient methods to test efficacy (more on that below), basically means you get more shots at a target hence more chances at succeeding. This is the same exact lesson the software industry learned about the importance of fast iterations. Companies like Starget Pharma are leveraging AI heavily to iterate on drug candidates + figured out in-house manufacturing in a way that lets them iterate on drugs almost as fast as if they were a software company iterating on features. 2. Real world testing: i.e. how fast can we get a call on a drug's efficacy. We need better real-world indicators for drug efficacy than mouse / animal models. The success rate of animal models -> human clinical trials is less than 8%. Breaking down this bottleneck will change the entire industry. Developing an oncology drug and taking it through all clinical trials usually cost >> $ 100m Thus taking the wrong bet is devastating (but still, happens a lot). Giving drug development companies the ability to better understand the efficacy and mechanisms of their drugs will change a lot. Esp in the age of abundant drug candidates. Furthermore - and once those methods proved efficient - Joining forces with regulators to shorten (or even skip) some clinical trials altogether will cut years from the process and save many lives by bringing new drugs to market faster. CuResponse is pioneering functional testing - taking real cancer biopsies and showing drug efficacy with very high precision. Can be used for precision oncology as well as testing new drugs. Cellint is providing a fully automated cell-culture R&D platform for companies and researchers. ---- I’d love to see a future where there are “cloud services” for drug development companies. A company should eventually be able to submit a drug candidate programmatically and receive: 1. The synthesized drug. 2. Testing across cells, tissues, organoids, and tumoroids. 3. Structured results showing what worked, what failed, and why. 4. A recommended next iteration derived from the biological reactions. I’ve invested in all of the above companies and am searching for additional companies to bring this “cloud services for drug dev” vision to life. ---- Alongside it, I am also investing in direct therapeutic moonshots. I invested in Baccine, which is developing a bacteria-based cancer immunotherapy platform and deserves an entire separate post. I’m also a proud LP in Even One Ventures - @sytses ’s fund to fight cancer. Sid and Jacob Stern are an inspiration to me as I’m making my first steps in the field, and I bet their companies will make a massive impact. And 3 other incredible companies focused on how therapies are delivered - where I’ll elaborate in future posts. ---- I’m still obviously spending most of my time on Base44. Which is a plus for the companies - as we’re able to support them with tools, software, AI agents, etc. I’m looking for people to join me - invest side by side or help one of the companies. I don’t have a name for the fund yet, nor an email or a website I will get to it this weekend and will post it in the comments.
115
88
1,520
234,623
Yoav Orlev retweeted
Over the last 6 months, @Base44 ran more than 5,000,000,000 automations for our users. Five billion. And with our new workflows capability, we're at a 0.07% error rate, dropping every single day. A few thoughts on how we got here: David Vaks from our team built an engineering wonder. making automations reliable at this scale isn't a feature, it's a distributed-systems problem most companies never have to face. He faced it head on. This is what Base44 is about. we don't pick the easy problems - we go after the hardest engineering challenges, because that's what it takes to let anyone build real software. And that's the bigger point: vibe coding isn't just the easiest way to build software anymore. It's becoming the most holistic one. your app, your data, your automations, your workflows, all in one place, built by describing what you want. 5 billion automations in. We're just getting started.
9
10
79
5,999
Yoav Orlev retweeted
Two teenagers built a $3M junk removal business. the app running the whole thing was built by another teenager on their team, on @base44. this is exactly what i built base44 for. the barrier was never the idea, it was everything between the idea and working software. developers, funding, months of building. vibe coding removes all of it. coding isn't the question anymore. only what you'll build is.
7
14
80
6,597
We just shipped a full partner stack in @Base44 . Thousands of people already run real client businesses on Base44. They've been building fast and shipping great work. Now the platform actually works for how they operate. What's live: Client messages. Every client request lands in one inbox inside Base44. Reply where the work happens. Link an app to a client straight from the conversation. Partner profiles. Your storefront on Base44. Showcase your apps, set your rates and response time, collect reviews. Partner channels. All Base44 partners in one place, inside the platform. Swap what works, team up on bigger builds. App ownership transfer. Project done? Hand the app to your client for good. Data, media, connected services included. It runs on their workspace and their plan. Unified workspace view. Every app you own, collaborate on, or administer. One list, across all client workspaces. Credit delegation. You choose which workspace pays. Work in a client's workspace on your own credits, or theirs. Partners were already winning on Base44. We just gave them a home field. Great work by the team - Raphael, Amit, Elior and Kris!
8
5
32
8,729