Today we’re introducing Base Code. It’s an early preview of how we think software will be built in the future. It’s a product that encapsulates everything we’ve learnt from: - How our users are building software. - How we’re building internally, scaling to hundreds of millions of dollars in revenue while keeping our engineering team very small and focused. Here are some of the principles behind it, which align with how we at @Base44 think about the future of software engineering: Cloud: - Software will move past local desktop environments (where current tools are widely used) and move to the cloud. - Moving everything to the cloud is not easy. Setting up dev environments with databases, infra components, services, mock data, etc. is easier said than done. - Base Code first scans your code repo and sets up everything - every infra component (databases, Redis, etc.) - in the cloud. It runs nonstop until your preview environment is ready. - From an enterprise standpoint, it’s also the logical thing to do: a centralized, governed dev environment instead of handing out keys and secrets to all team members. - Once Base Code does that, EVERY team member can work in this environment. No more syncing local environments. Internally, this (cloud) is one of the main things that enabled us to move so fast. Collaboration: - Once everything is in the cloud, everybody can write software from anywhere (any browser, your phone, WhatsApp / iMessage coming soon). - You can easily see what everyone is working on, where they’re at, and how they’re prompting - and jump to their environment in one click. - We’ve built many great collaboration features from the ground up. Loops, automations, software factories: - A full, working cloud environment allows for many advanced capabilities we will unveil soon-think agents running in the browser and testing on every device and in any browser. - It also allows the use of automations to build software factories-e.g., agents reading support tickets, identifying bugs to fix or features to develop, implementing the changes, verifying them in the cloud, and potentially pushing them. And lastly, there’s a real advantage in being model agnostic. -------------- As always, we’re releasing it very early. It’s far from perfect-but we’re looking for early feedback so we can build it together with our great community and make this vision a reality. *We’re giving it away for free for 30 days*. Give Base Code a try. Connect any GitHub repo, get your live preview, and share it with your team. I’d love to hear what works and what doesn’t: app.base44.com/base-code

Today we're launching RouterGrowth, OpenRouter for sales Your agent can write code. It still can't find you a customer The data it needs is spread across 50 tools, 50 logins and 50 subscriptions We put it behind one key/MCP: intent signals, contacts, email, LinkedIn, WhatsApp and more Pay per call - Just Jell it

so i earned money from a claude code session today lol @PublicAI_ made this open source CLI called trajector. it runs as a local proxy between your claude code and the API, records your sessions, redacts your secrets on your machine, and uploads the clean data. you get credited per session based on your tokens. after setup i just coded normally. ran one prompt on opus 5, built a markdown preview tool in 4 minutes, and when i checked the dashboard $0.02 was sitting there. i literally changed nothing about how i work. it just runs in the background on projects you opt into. $0.02 is tiny but i use claude code every single day so i'm curious to see where this goes if you use claude code check it out here docs.publicai.io/publicai-do…

Introducing ScienceBuddy — a free workspace for scientific agents that improve through researcher collaboration. Use GPT-6 in ScienceBuddy at no cost. GPU-accelerated, and fused with the JEV framework. 🧵 Two loops: 🔹 Inner loop — refines the agent harness 🔹 Outer loop — trains the model with rubric-guided RL Together: Recursive-in-Recursive Self-Improvement. ScienceBuddy explores how scientific agents can improve through sustained collaboration with researchers. 🔬Try it free: science-buddy.io #ScienceBuddy #PhAILabs #AI4Science

so i earned money from a claude code session today lol @PublicAI_ made this open source CLI called trajector. it runs as a local proxy between your claude code and the API, records your sessions, redacts your secrets on your machine, and uploads the clean data. you get credited per session based on your tokens. after setup i just coded normally. ran one prompt on opus 5, built a markdown preview tool in 4 minutes, and when i checked the dashboard $0.02 was sitting there. i literally changed nothing about how i work. it just runs in the background on projects you opt into. $0.02 is tiny but i use claude code every single day so i'm curious to see where this goes if you use claude code check it out here docs.publicai.io/publicai-do…

EXCITED TO LAUNCH: Akai (akai.run) Deel added >$140M ARR in 90 days without increasing headcount by automating~600 Full Time Employees' equivalent in work with Akai. Akai was an internal tool to automate our painfully repetitive operations in Finance, HR, Accounts Payable, and Compliance, etc. We never intended to make this a product. But we watched revenue per employee grow from $130K to $215K We built >8k agents that do the work of ~600 employees It had such a dramatic impact on our business that today we are launching it for everyone. How it works: Say you're automating payment reconciliation: 1. Record your screen while manually matching a messy transaction and Akai will capture your screen, voice, server requests 2. Akai will see that you pulled unformatted wire transfer info from an archaic bank portal, put it in some excel sheet, checked NetSuite invoices, payment history, and put a ticket on Zendesk 3. Akai reads between the lines and build a workflow + steps + conditional guardrails. It learns tacit edge cases, like resolving malformed invoice references without you writing a single regex 4. Simply connect NetSuite, your ledger, Zendesk, PSPs, and even legacy bank portals with zero API access 5. Run the workflow and tell it what to adjust in plain English: "strip slashes on wire memos and auto-apply partial payments." It adapts instantly 6. Once it works for you, add 100s of colleagues. Your entire payment ops team forks and extends the workflow for new PSPs, secondary ledgers, or regional settlement rules 7. We automated 85% of our payment reconciliation end to end, eliminating 500+ hours of soul-crushing manual grunt work every single week. Claude Code/Codex can't do this in multiplayer mode. Every person rebuilds the same skill from scratch in their own way. Deel built Akai to: 1. Understand backend operations edge cases (it had to work for our 7000 person team first) 2. Collaborative across 1000s of employees 3. Self-Learning from millions of runs 4. Optimises cost and gets cheaper every run We're so confident that we're announcing an Automation Guarantee: If our engineers can't automate a thousand of hours of work in your first 30 days, you get a full refund. Book a demo: akai.run if you're an exec at a company with hundreds of employees

Meet Moonphase Flip: a low-distraction AI screen on the back of your phone that keeps track of your to-dos and takes actions before you ask. Threads below 🧵 Explore more: hellomoonphase.com/s/17e982