# Low-Code / Internal Tools Low-code and internal tools for building admin panels and internal applications without full-stack engineering. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Six Months vs Six Days: The True Cost of Building Internal Tools DevFeed: [Six Months vs Six Days: The True Cost of Building Internal Tools]() Original publisher: [Read original article]() Author: Daria Kvasnytska Published: 2026-09-01T03:00:00Z Content type: opinion Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [Low-Code / Internal Tools](), [Low code](), [Development](), [Software Engineering]() Tags: [community](), [cost](), [cypex](), [development](), [internal-tools](), [low-code](), [product](), [software](), [tools]() ### AI overview The article examines the direct, opportunity, and maintenance costs of building internal tools, arguing that seemingly small projects can expand beyond their planned scope and reduce time available for customer-facing product work. It also discusses low-code platforms, focusing on data and application ownership, vendor lock-in, and enterprise pricing. ### Source excerpt This blog is about how CYPEX can cut costs on building internal tools. The post Six Months vs Six Days: The True Cost of Building Internal Tools appeared first on CYBERTEC PostgreSQL | Services & Support. ## How to run an internal-tools demo night: WorkOS field notes DevFeed: [How to run an internal-tools demo night: WorkOS field notes]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-28T12:52:51Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Low-Code / Internal Tools](), [Demo](), [Tooling]() Tags: [2026](), [demo](), [how-to](), [internal-tools](), [talks]() ### AI overview WorkOS shares field notes from running two internal-tools showcases. The playbook covers a sequenced lineup of five short talks, live demonstrations, a single panel Q&A, audience mingling, and contingency planning for presenter and demo failures. ### Source excerpt Field notes from running the WorkOS internal-tools showcase twice: five talks, live demos only, one Q&A, a sequenced lineup, and a contingency for every demo. ## From Vibe Coding to the AI Software Factory DevFeed: [From Vibe Coding to the AI Software Factory]() Original publisher: [Read original article]() Author: SeattleDataGuy Published: 2026-08-26T22:10:01Z Content type: opinion Language: en Sources: [SeattleDataGuy's Newsletter]() Topics: [Artificial Intelligence](), [Large Language Model](), [Vibe coding](), [coding](), [Low-Code / Internal Tools]() Tags: [ai](), [developers](), [engineering](), [llms](), [vibe-coding]() ### AI overview The article examines how engineering teams progress from using LLMs for code completion and isolated experiments toward standardized, repeatable systems for producing software with AI. It describes this progression as a spectrum of software-factory practices and argues that many companies remain at the stage of disconnected individual workbenches and one-off macros. ### Source excerpt How I've Seen Engineering Teams Use LLMs Over The Past Few Years ## How WorkOS Lets Domain Owners Build Internal AI Tools DevFeed: [How WorkOS Lets Domain Owners Build Internal AI Tools]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-24T14:42:28Z Content type: opinion Language: en Sources: [WorkOS Blog]() Topics: [Artificial Intelligence](), [Low-Code / Internal Tools](), [Tooling]() Tags: [agents](), [ai](), [applied-ai](), [claude](), [internal-tools](), [tooling]() ### AI overview This commentary describes WorkOS's approach to internal AI tooling, in which domain owners build agents and tools for problems they understand firsthand while the platform team provides shared infrastructure and access controls. It highlights examples including Wallaby, Blog Bot, the CLI, and Horizon, and reports that 39 apps shipped to production during Claude Day. ### Source excerpt Internal AI tooling inverted the internal-tools org chart. Domain owners build their own agents, and the platform team now ships substrate and access controls. ## WorkOS Applied AI Showcase July 28 2026 - Moving to an AI-native Organization DevFeed: [WorkOS Applied AI Showcase July 28 2026 - Moving to an AI-native Organization]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-14T13:36:57Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Artificial Intelligence](), [Low-Code / Internal Tools](), [AI-assisted coding](), [Containers](), [MCP](), [Command-line interface](), [incident](), [Security](), [datadog](), [Pull Request](), [Slack](), [GitHub]() Tags: [agent](), [agents](), [ai](), [applied-ai](), [cli](), [coding](), [coding-agents](), [containers](), [datadog](), [demo](), [event](), [github](), [incident](), [internal-tools](), [mcp](), [organization](), [pull-request](), [slack](), [talks](), [team]() ### AI overview WorkOS's Applied AI Showcase in New York presented five internal tools--Horizon, Blog Bot, the CLI, Wallaby, and Atlas--through live demos and talks. The article explains how the Applied AI team helps non-engineering functions build AI-powered workflows and systems. ### Source excerpt WorkOS is becoming an AI-native organization. The Applied AI Showcase in NYC on July 28th 2026 showed exactly how with live demos and talks from the Applied AI team. ## AI fluency isn't the finish line DevFeed: [AI fluency isn't the finish line]() Original publisher: [Read original article]() Author: Andrew Hogan Published: 2026-07-31T21:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Artificial Intelligence](), [Low-Code / Internal Tools](), [interactive website](), [Figma]() Tags: [ai](), [ai-tools](), [developers](), [interactive-website](), [internal-tools]() ### AI overview The article argues that AI fluency is only one part of adapting to AI-shaped work. It emphasizes shared systems, collaboration, facilitation, and turning individual knowledge into reusable team tools such as internal tools, plugins, prompt libraries, and interactive websites. ### Source excerpt More than 90% of product builders say AI skills are essential to their future success. But what if we're focused on the wrong ones? ## Leading design through the AI shift DevFeed: [Leading design through the AI shift]() Original publisher: [Read original article]() Author: andyacevedo Published: 2026-05-21T16:47:34Z Content type: opinion Language: en Sources: [Slack Design]() Topics: [Artificial Intelligence](), [AI-assisted coding](), [Code](), [Data analysis](), [Low-Code / Internal Tools](), [Tooling](), [ui]() Tags: [agents](), [ai](), [ai-tools](), [coding-agents](), [data-analysis](), [figma](), [internal-tools](), [ui](), [uncategorized](), [workflow]() ### AI overview A Slack Design leader describes how AI is changing the team's design workflow, including the use of coding agents for data analysis and rapid prototyping, code-based demos, and designer-built internal tools. The article emphasizes combining AI tools with human judgment and taste while acknowledging increased stress, uncertainty, and ethical questions. ### Source excerpt AI has eaten the technology industry. What started as a slow, hallucination-prone chatbot has become something much harder to ignore. As a designer, it can feel like the ground is shifting under your feet, quietly at first, then all at once. Every week, something new disrupts your workflow, your toolset, your expectations about what's possible. [...] The post Leading design through the AI shift appeared first on Slack Design. ## Taming chaos is a learnable skill DevFeed: [Taming chaos is a learnable skill]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-03-11T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Software Engineering](), [engineering-culture](), [Low-Code / Internal Tools]() Tags: [approach](), [chaos](), [engineering](), [exceptions](), [internal-tools](), [operations](), [software-engineering](), [startup]() ### AI overview The article argues that handling interruptions, operational surprises, exceptions, and changing priorities is a learnable software-engineering skill. It recommends owning system problems, managing scope and tradeoffs, validating quality requirements, and maintaining a long-term vision despite short-term disruption. ### Source excerpt How you approach software engineering makes it harder or easier to handle interruptions and other chaos. Writing a behavioral interview made me realize this is a learnable skill! ## Introducing the Visual Studio Code Private Marketplace: Your Team's Secure, Curated Extension Hub πŸŽ‰ DevFeed: [Introducing the Visual Studio Code Private Marketplace: Your Team's Secure, Curated Extension Hub πŸŽ‰]() Original publisher: [Read original article]() Author: Sean Iyer Published: 2025-11-18T00:00:00Z Content type: article Language: en Sources: [Visual Studio Code - Code Editing. Redefined.]() Topics: [Visual Studio Code](), [Extension](), [GitHub](), [Deployment](), [Security](), [Low-Code / Internal Tools](), [hosting]() Tags: [2025](), [article](), [blog](), [deployment](), [developers](), [extensions](), [github](), [hosting](), [internal-tools](), [security](), [visual-studio](), [vs-code]() ### AI overview The article introduces Private Marketplace for Visual Studio Code, an enterprise-ready service for curating, privately hosting, rehosting, and centrally distributing extensions to development teams. It is available to GitHub Enterprise customers and requires eligible GitHub Enterprise or Copilot accounts. ### Source excerpt Private Marketplace for VS Code extensions now generally available. Read the full article ## Building the Web that Moves Money: inside Web engineering at Revolut DevFeed: [Building the Web that Moves Money: inside Web engineering at Revolut]() Original publisher: [Read original article]() Author: Revolut Published: 2025-10-16T09:45:59Z Content type: article Language: en Sources: [Revolut Engineering]() Topics: [Web Development](), [modern web development](), [web applications](), [Low-Code / Internal Tools](), [Agile]() Tags: [agile](), [applications](), [building](), [engineering](), [fintech](), [internal-tools](), [modern-web-development](), [revolut](), [web](), [web-applications](), [web-development](), [web-engineering]() ### AI overview Revolut describes its web engineering approach across customer-facing products and roughly a hundred internal web applications. The article discusses secure financial experiences, modern development practices, small empowered teams, and agile principles inspired by Extreme Programming. ### Source excerpt Building the Web that moves money: inside Web engineering at RevolutIntroduction In today's digital-first economy, the web is the critical touchpoint between people and their money. At Revolut, we embrace this reality in our approach to web engineering: focusing on not just building interfaces, but on creating seamless, secure, and future-proof financial experiences. Our mission at Revolut is to redefine the global standard for digital finance. Every line of code, design decision, and feature we release serves this goal: to make finance more accessible and beautifully engineered. These principles shape our culture, set a high standard for excellence, and require constant attention to detail. They also drive us to rethink modern web development tools and practices. This article focuses on the principles that help us deliver secure, beautiful financial products worldwide, and explains how engineers are building their careers along the way. The scope of Revolut web products Two independent but complementary pillars represent the current stage of the Revolut web ecosystem. Customer-facing applications These are the digital gateways through which our customers and partners experience Revolut directly: Main website and brand hub Revolut Business platform Revolut crypto exchange platform Human Resources Management Systems (HRMS) by Revolut Each of these touchpoints is an individual part of a unified ecosystem offering a consistent product experience that is closely aligned with our mobile platform. Internal web products Alongside our external platforms, Revolut operates around a hundred internal web applications. These provide our employees, operations, and partners with tools for: Back-office management Compliance and risk monitoring Customer support services Data and reporting systems Operational efficiency at scale These internal tools are the driving force behind Revolut, ensuring customer-facing products remain fast, secure, and globally scalable Core principles of we ## Postgres as Your Platform: Building Event-Driven Systems with Schema Changes DevFeed: [Postgres as Your Platform: Building Event-Driven Systems with Schema Changes]() Original publisher: [Read original article]() Author: Andrew Tate Published: 2025-07-25T19:46:32Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Database](), [event driven](), [Structured-data](), [Low-Code / Internal Tools](), [SDKs](), [TypeScript](), [Software as a service](), [Internet of things](), [dashboards]() Tags: [dashboards](), [event-driven](), [iot](), [platform](), [postgres](), [saas](), [schema](), [sdks](), [typescript]() ### AI overview This article presents Postgres as an event-driven platform rather than merely a database. It explains how transactional DDL, event triggers, LISTEN/NOTIFY, extensions such as pgvector and pg_cron, and other native features can automate schema-related workflows, including SDK generation, data warehouse synchronization, and dashboard updates. ### Source excerpt For years, we've built elaborate scaffolding around our databases: message queues to broadcast changes, cron jobs to sync schemas, webhooks to notify downstream systems. We needed this scaffolding because Postgres was "just" a database, a place to store rows and run queries. The... ## Build Internal Tools Using Neon, StackAuth, and Vercel DevFeed: [Build Internal Tools Using Neon, StackAuth, and Vercel]() Original publisher: [Read original article]() Author: Sam Harrison Published: 2025-07-08T16:22:43Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Low-Code / Internal Tools](), [Vercel](), [App](), [Database](), [Authorization](), [Authentication](), [API]() Tags: [api](), [app](), [auth](), [authentication](), [authorization](), [build](), [community](), [database](), [env-file-security](), [environment-variables](), [internal-tools](), [vercel]() ### AI overview This article presents a template for building internal tools with Neon, StackAuth, and Vercel. The template includes a Postgres database, API routes, authentication, authorization, and an admin panel, with setup instructions covering environment variables, database synchronization, local startup, access configuration, and deployment. ### Source excerpt Almost every tech company, from small startups to Fortune 500 enterprises relies on internal tools. Larger organizations often have dedicated services and structured procedures in place, but for many others, internal tools are... messy. They often take the form of an insecure setup... ## Fibery vs. Notion 2025: not Better, Different DevFeed: [Fibery vs. Notion 2025: not Better, Different]() Original publisher: [Read original article]() Author: Michael Dubakov Published: 2025-04-11T07:52:12Z Content type: comparison Language: en Sources: [Stories by Michael Dubakov on Medium]() Topics: [Notion](), [knowledge-management](), [Product Management](), [Wiki](), [Low-Code / Internal Tools]() Tags: [2025](), [automation](), [notion](), [permissions](), [processes](), [product-management](), [productivity](), [saas-tools](), [tools-for-thought](), [visualization](), [vs](), [wiki]() ### AI overview A founder-authored comparison explains that Fibery and Notion serve different use cases rather than one being universally better. It presents Notion as well suited to personal knowledge management, company wikis, knowledge bases, and simple processes, while describing Fibery as better suited to complex processes with deeper hierarchies, relations, permissions, formulas, automations, and advanced visualizations. ### Source excerpt Disclaimer: This post is written by Fibery Founder, so it is inevitably biased (but I tried to be as objective as I can). You came here to find out how πŸ‰ Fibery is better than 🐼 Notion. Well, it is not. Fibery is different. Notion is a great tool and it works exceptionally well for some use cases, but it fails for others. Let me just quickly answer your main question and then feel free to dig into details later. 🐼 What Notion is great for? Personal knowledge management (PKM) Company wiki and knowledge base Simple (not complex) processes: basic project management, basic CRM, basic candidates tracking, etc. "I've been using Notion for the past few years. It's undoubtedly the most flexible note-taking app on the market. Offering both simplicity and complexity, it caters to a variety of users. Its recent integration with AI and automation further elevates the note-taking experience. Imagine having your own personal Wikipedia, comprehensive databases, calendar, tasks, calculator, and more, all within a single app. This truly makes Notion the best of the best." -- Notion userπŸ‰ What Fibery is great for? Company wiki and knowledge base Complex processes: product management, feedback management, portfolio management, OKR, HR, Vacation tracking, etc. "We use Fibery to manage all our startup processes, from customer discovery over HR until CRM, Project management and documentation. We could replace 27 of our 36 internal tools: Fibery is a rocket for managing all sorts of processes and lets us the freedom to create our own templates and spaces aka processes, if needed." -- Fibery user It can be illustrated like this: Notion and Fibery areas of best applicability Fibery will help you when Notion is just not enough. When you need deep hierarchies and relations, advanced access and permissions control, formulas and automations across these hierarchies, visualization of information in hierarchical timelines and table views, complex charts. In general, Fibery is harder to "get" and ma ## Tophat: Crafting a Delightful Mobile Developer Experience DevFeed: [Tophat: Crafting a Delightful Mobile Developer Experience]() Original publisher: [Read original article]() Author: Lukas Romsicki Published: 2024-08-23T17:16:27Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Developer experience](), [Shopify](), [Low-Code / Internal Tools](), [Pull Request](), [Code review](), [GitHub](), [macOS](), [React Native](), [Command-line interface]() Tags: [cli](), [code](), [developer-experience](), [internal-tools](), [macos](), [mobile](), [pull-request](), [react-native](), [review](), [shopify]() ### AI overview Shopify describes Tophat, a macOS menu bar app that streamlines manual testing of mobile changes from GitHub pull requests. The tool evolved from a CLI-based workflow into an interactive desktop experience designed to improve developer productivity and confidence while Shopify migrates its mobile codebase to React Native. ### Source excerpt Insight into how Shopify created a seamless one-click manual testing experience (known as "tophatting") for mobile applications by creating a macOS app. ## Two years of Next.js at Artsy: A Retrospective DevFeed: [Two years of Next.js at Artsy: A Retrospective]() Original publisher: [Read original article]() Published: 2024-03-07T00:00:00Z Content type: opinion Language: en Sources: [Artsy]() Topics: [Next.js](), [Framework](), [Low-Code / Internal Tools](), [Front end](), [JavaScript](), [TypeScript](), [Authentication](), [Databases]() Tags: [authentication](), [framework](), [front-end](), [internal-tools](), [javascript](), [next-js](), [react](), [typescript]() ### AI overview Artsy recounts two years of using Next.js, including a hackathon proof of concept for deduplicating artist records and a subsequent rebuild of a complex internal tools application. The article credits Next.js's conventions, framework-level setup, and documentation with helping a platform engineering team deliver core functionality, while noting remaining work around authentication and runtime secrets. ### Source excerpt Where to begin! Where to begin... Lets start with a good measure of success, one that I think most engineers could agree on: a from-scratch rebuild of a complex, internal tools app. Success with rebuilds is often fleeting, as many can attest. There's risk involved. Extending the challenge further, lets assign (most) of the task to a team of platform engineers who aren't too familiar with modern front-end technology - and then say that we succeeded. Is Artsy crazy? Or is Next.js (along with our team πŸ™‚) just that good? Well, it's a little of both. And it's a little bittersweet, in a way. Here's our tale. Beginnings Our first formal use of Next came from a project spun up during Hackathon, two years ago. Hackathon's are great opportunities to push technology forward, and Artsy has had a lot of success with them. We'd been talking about Next.js for a while, and experimenting here and there, but we were never able to find the proper intersection of product and purpose to take things further. With this in mind, one of our Engineers (Roop πŸ‘‹) spun up a Next.js POC that allowed us to deduplicate artist records. On the surface, the effort was non-trivial. It involved authentication, DB communication, and more. Yet when presented during Hackathon, all of this was done and it also looked beautiful. How could so much product work get completed in such a short period of time? A large part of that is due to Next.js's framework design, and how it simply gets out of the way and allows one to start building product features. The defaults made sense; to create a new route, simply create a new folder or file in the pages directory, and Next takes care of the rest. And what about compilation, TypeScript, linting, and all of the other extraordinarily confusing JavaScript toolchain details that folks typically struggle over? (Most) of the setup was taken care of at the framework level, and the API side of things was light and easy to understand, thanks to great documentation. There are omit ## How to build AI-powered apps using Postgres and DronaHQ DevFeed: [How to build AI-powered apps using Postgres and DronaHQ]() Original publisher: [Read original article]() Author: Aaikansh Agrawal Published: 2024-01-17T12:15:36Z Content type: tutorial Language: en Sources: [Blog -- Neon Docs]() Topics: [Low code](), [Artificial Intelligence](), [Low-Code / Internal Tools](), [Databases](), [Front end](), [OpenAI]() Tags: [ai](), [ai-apis](), [ai-models](), [apis](), [applications](), [article](), [community](), [dashboards](), [data](), [database](), [developers](), [forms](), [frontend](), [how-to](), [internal-tools](), [low-code](), [no-code](), [openai]() ### AI overview This article explains how low-code tools can help developers build internal, AI-powered applications. It describes connecting stored lead data and databases to unified frontends, forms, workflows, tables, dashboards, and AI APIs or models that generate personalized email content. The supplied text ends while beginning a demonstration involving Neon and DronaHQ. ### Source excerpt AI, no-code, and low-code have captured the world's imagination. Developers now have an easier time adding new features than ever before. These new tools have really made a difference for developers, helping them build bigger systems, and do it all much faster. In this article, I... ## How To Measure the Value of Internal Tools DevFeed: [How To Measure the Value of Internal Tools]() Original publisher: [Read original article]() Author: Chang Liu Published: 2023-08-02T16:00:00Z Content type: tutorial Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [Low-Code / Internal Tools](), [Data analysis](), [data-processing]() Tags: [analysis](), [collect](), [collection](), [cost](), [data-analysis](), [data-science](), [efficiency](), [engineering](), [how-to](), [internal-tools](), [metrics]() ### AI overview This tutorial introduces Square's internal products and explains how to measure their effectiveness using internal metrics. It discusses evaluating impact, improving features with data, identifying anomalies, and designing appropriate data collection processes for different types of tools. ### Source excerpt Introduction to Square internal products and the metrics we use to track their effectiveness ## New Joiner: Sam Starling DevFeed: [New Joiner: Sam Starling]() Original publisher: [Read original article]() Author: incident.io Published: 2022-11-01T00:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident management](), [incident](), [Low-Code / Internal Tools](), [Tech Lead]() Tags: [development](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [internal-tools](), [outage](), [post-mortem](), [slack-incident](), [tech](), [tech-lead]() ### AI overview Sam Starling joins incident.io as a Product Engineer after working at Monzo and SoundCloud. He brings experience with user growth, referrals, customer onboarding, internal tools, and incident management. ### Source excerpt Welcoming Sam Starling to the team! ## You can use SwiftUI today DevFeed: [You can use SwiftUI today]() Original publisher: [Read original article]() Published: 2020-01-04T02:50:00Z Content type: opinion Language: en Sources: [Rambo Codes]() Topics: [SwiftUI](), [iOS](), [Low-Code / Internal Tools](), [macOS](), [Risk]() Tags: [internal-tools](), [ios](), [macos](), [risk](), [swift](), [swiftui]() ### AI overview The author argues that using SwiftUI immediately for App Store production apps is risky because the technology is new, has rough edges, and may change significantly. They nevertheless recommend that iOS developers learn SwiftUI through substantial hands-on projects, including internal tools, rather than only tutorials or small test projects. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures.