# Internal Tools Published articles for Internal Tools. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Protect production deployments for free on every plan DevFeed: [Protect production deployments for free on every plan]() Original publisher: [Read original article]() Author: Jas Garcha Published: 2026-09-09T06:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Deployment](), [Authentication](), [Security](), [dashboards](), [Low-Code / Internal Tools]() Tags: [authentication](), [dashboards](), [deployment](), [internal-tools](), [password](), [security](), [vercel]() ### AI overview Vercel now lets every plan protect all project deployments, including production, with Vercel Authentication at no extra cost. The update also makes deployment protection exceptions free and lets Pro teams enable password protection per project. ### Source excerpt Vercel Authentication can now protect all deployments in a project, including production, at no additional cost on every plan. Previously, protecting production domains required the $150-per-month Advanced Deployment Protection add-on. When enabled, visitors must sign in with a Vercel account that has access to the project. This makes it useful for internal tools, private dashboards, and sites that aren't yet ready to launch. From your project, open Security in the sidebar, select Deployment Protection, then choose All Deployments from the dropdown. You can also make this the team default, so every new project starts with Vercel Authentication enabled for all deployments. With this change: Deployment Protection Exceptions are now free on every plan. Use an exception to make a specific preview domain public while keeping the rest of the project protected. Pro teams can now enable Password Protection for individual projects instead of purchasing it for the entire team. Learn more in the Deployment Protection documentation. Read more ## 1Password increases engineering productivity 21% with Codex DevFeed: [1Password increases engineering productivity 21% with Codex]() Original publisher: [Read original article]() Published: 2026-09-08T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [AI-assisted coding]() Tags: [codex](), [engineering](), [features](), [internal-tools](), [productivity](), [pull-request](), [security](), [site-reliability-engineering](), [software-delivery](), [user-stories](), [writing-code]() ### AI overview 1Password reports using Codex across its software delivery lifecycle to turn user stories into near-final prototypes and features more quickly. It cites improved engineering productivity and shorter pull request cycle times while maintaining security standards. ### Source excerpt Engineers at 1Password use Codex to rapidly build new features and internal tools, reaching production-readiness while maintaining rigorous security policies. ## 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. ## 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. ## From all-or-nothing to task-based OAuth consent DevFeed: [From all-or-nothing to task-based OAuth consent]() Original publisher: [Read original article]() Author: José Enrique Rodríguez Published: 2026-08-20T17:03:03Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [Authorization](), [Security](), [Cloudflare](), [MCP Server](), [App](), [Low-Code / Internal Tools](), [Software as a service]() Tags: [agent](), [agents](), [api](), [applications](), [cloudflare](), [developer-platform](), [developers](), [identity](), [integrations](), [internal-tools](), [mcp](), [mcp-server](), [oauth](), [product-news](), [security](), [workflows]() ### AI overview Cloudflare OAuth now supports customizable consent scopes, allowing users to grant only the optional permissions needed for a specific task while developers retain required scopes. ### Source excerpt Cloudflare OAuth now supports optional scopes, giving users more control over what an app can access and helping developers build secure consent flows around the task at hand. ## 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? ## Three internal tools Datadog built with AI that improved developer experience and system performance DevFeed: [Three internal tools Datadog built with AI that improved developer experience and system performance]() Original publisher: [Read original article]() Author: Joe McGovern; Alex Zvorygin; Alex Bianchi; Colin Nichols Published: 2026-07-01T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [developer tooling](), [Deployment Tools](), [Orchestration](), [AI Bots](), [SDKs](), [sdlc]() Tags: [ai](), [bits-ai](), [deployment-tools](), [developer-experience](), [devops](), [internal-tools](), [orchestration](), [performance](), [platform-engineering](), [sdlc](), [software-delivery](), [testing]() ### AI overview Datadog describes internal AI-enabled tools intended to improve developer experience, deployment support, and backend performance. One example is an agent-orchestrated support application that investigates deployment requests, drafts responses for approval, and can open a pull request when it identifies a potential fix. ### Source excerpt At Datadog, we don't just use AI to ship customer products. It also enables internal projects and performance wins that help our engineers and systems do their jobs better and faster. Learn more in this blog. ## 5 Tips to Save Money on Laravel Cloud DevFeed: [5 Tips to Save Money on Laravel Cloud]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-06-05T15:30:22Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Cloud](), [Cache](), [Databases](), [Livewire](), [Low-Code / Internal Tools]() Tags: [app](), [apps](), [billing](), [business](), [cache](), [cloud](), [compute](), [cost](), [database](), [databases](), [developer](), [growth](), [internal-tools](), [laravel](), [operations](), [pricing](), [reduce](), [resource](), [resources](), [scale]() ### AI overview Five ways to reduce Laravel Cloud costs: enable scale to zero for Flex compute, set an organization spending limit, monitor the usage page, use managed queues, and share databases and caches across apps. ### Source excerpt Five ways to reduce your Laravel Cloud bill: enable scale to zero, set a spending cap, use the usage page, switch to managed queues, and share resources. ## Travelers deploys AI-powered claims countrywide with OpenAI DevFeed: [Travelers deploys AI-powered claims countrywide with OpenAI]() Original publisher: [Read original article]() Published: 2026-06-02T12:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [AI Chat](), [Orchestration]() Tags: [ai](), [api](), [autonomous](), [customer](), [enterprise](), [infrastructure](), [internal-tools](), [models](), [openai](), [operations](), [orchestration](), [real-time](), [scale](), [support](), [voice]() ### AI overview Travelers deployed an autonomous voice AI Claim Assistant using the OpenAI Realtime API and frontier models to guide customers through auto property-damage claim filing. The company connected the models to claims infrastructure and internal tools to provide 24/7 support at enterprise scale. ### Source excerpt Travelers built an AI-powered Claim Assistant with OpenAI to guide customers through filing claims, provide 24/7 support, and scale operations during peak demand. ## 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 ## How CRED is tapping AI to deliver premium customer experiences DevFeed: [How CRED is tapping AI to deliver premium customer experiences]() Original publisher: [Read original article]() Published: 2025-11-05T21:30:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [AI Chat](), [AI, ML & Data Engineering]() Tags: [ai](), [api](), [customer](), [gpt](), [india](), [internal-tools](), [openai](), [support]() ### AI overview CRED describes using OpenAI-powered conversational and internal tools to improve customer support, operational workflows, and premium customer experiences. ### Source excerpt CRED is improving premium customer experiences in India with OpenAI, using GPT-powered tools to boost support accuracy, cut response times, and raise customer satisfaction. ## 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 ## Retool Becomes the Platform for Enterprise AppGen DevFeed: [Retool Becomes the Platform for Enterprise AppGen]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2025-10-07T16:42:35Z Content type: news Language: en Sources: [Blog -- Neon Docs]() Topics: [Retool](), [AI-assisted coding](), [AI Bots]() Tags: [ai](), [apis](), [code-generation](), [compliance](), [databases](), [enterprise](), [internal-tools](), [product](), [retool]() ### AI overview Retool announces Enterprise AppGen and its public-beta Assist capability, which generates queries, UI, and workflows for internal tools using enterprise data and existing governance controls. ### Source excerpt Retool has long been the platform teams turn to for building internal software fast. At this year's Retool Summit, they announced a big step forward - a new generation of AI-powered capabilities designed to take that speed to another level. They call it enterprise AppGen. Now, en... ## 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... ## Developing an Internal Tool for Our Puzzle Editor DevFeed: [Developing an Internal Tool for Our Puzzle Editor]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2025-06-02T15:54:44Z Content type: article Language: en Sources: [New York Times]() Topics: [dashboards](), [Data Management](), [interface](), [payload](), [Testing](), [Tool]() Tags: [code](), [dashboard](), [data-management](), [developing](), [interface](), [internal-tools](), [payload](), [puzzle](), [testing](), [tool](), [web-development](), [workflow]() ### AI overview The article describes how The New York Times developed the Connections Reference Dashboard, an internal tool for managing puzzle data and supporting the Connections editor's workflow. It explains the tool's interface, handling of changing puzzle data, search capabilities, and reduction of manual cross-referencing steps. ### Source excerpt How we developed a dashboard tool created to help ease the workflow of managing puzzles for our Connections editor.Illustration by Su Yun Song By Shafik Quoraishee and Wyna Liu In the game Connections, every puzzle is a meticulously crafted challenge designed to captivate our audience and spark intellectual curiosity. Developing these puzzles can sometimes be a time consuming and intricate task. Each puzzle requires planning, beginning with conceptualizing fresh categories and plausible misleads, followed by testing the combinations for balance and solvability, and concluding with refinement and publication-ready formatting. The process requires both creativity and quality control. Wyna Liu, the editor of Connections has the responsibility of constructing and reviewing multiple puzzles spanning various dates, ensuring that each board remains consistent, fresh and challenging to our puzzle solvers. This is a challenging endeavor where there isn't much room for error. In order to address the challenge, we developed the Connections Reference Dashboard -- an in company tool aimed at streamlining data management while providing the puzzle editor with an intuitive, aesthetically pleasing interface that enhances the daily workflow. There were two considerations in developing this tool. Firstly was technical work in handling a dynamically changing payload of puzzle data. We wanted to create a rich and visually resonating interface that was easy to navigate and gave a bit of the feel of the Connections game itself. Therefore, everything from the board results to the search interface was designed with these ergonomics in mind. We wanted to create a level of tactility to the tool which was reminiscent of and which reduced the number of manual steps needed to cross reference both categories and words in individual boards. The primary functionality that Wyna was after was the ability to quickly identify words that have appeared in previous Connections boards, as well as their con ## 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. ## Rubric Labs can make your AI dreams come true DevFeed: [Rubric Labs can make your AI dreams come true]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2024-08-23T15:49:08Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Developer experience](), [Serverless](), [autoscaling](), [GitHub](), [Open Source]() Tags: [autoscaling](), [case-studies](), [developer-experience](), [github](), [internal-tools](), [open-source](), [postgres]() ### AI overview Rubric Labs, an applied AI lab, uses Neon as a serverless Postgres database for internal and client projects. Its branching, autoscaling, and scale-to-zero features support isolated developer environments, parallel full-stack experimentation, and faster development workflows. The team also builds internal tools with Neon and uses it in SyncLinear, an open-source project that syncs Linear tickets with GitHub. ### Source excerpt "We absolutely love Postgres, but we prefer not using AWS or GCP because they are not developer-first. We use PlanetScale for MySQL projects, but for Postgres, we didn't have an equivalent where we could get the same level of developer experience... Until we found Neon" Sarim Malik... ## How Retool uses Retool (and the Neon API) to manage 300K+ Postgres databases DevFeed: [How Retool uses Retool (and the Neon API) to manage 300K+ Postgres databases]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2024-03-29T18:03:27Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Retool](), [backend-development]() Tags: [api](), [case-studies](), [databases](), [internal-tools](), [management](), [postgres](), [retool](), [serverless]() ### AI overview Retool uses Neon's API and serverless Postgres offering to provide managed databases within its internal-app platform. The article describes the goal of scaling a large database fleet with minimal engineering overhead through dedicated Postgres URLs for end users. ### Source excerpt Neon is a serverless Postgres database with a robust API. Partners like Retool choose Neon to easily offer managed databases to their end-users, simplifying the management of massive database fleets while optimizing costs. Thanks to Neon, Retool is able to manage over 300k Postgr... ## Running a k0s cluster with the GCP cloud controller for internal tooling DevFeed: [Running a k0s cluster with the GCP cloud controller for internal tooling]() Original publisher: [Read original article]() Published: 2024-03-12T00:00:00Z Content type: tutorial Language: en Sources: [Andika Ahmad Ramadhan -- Blog]() Topics: [Kubernetes](), [Cloud](), [Orchestration](), [Tooling]() Tags: [cloud](), [clusters](), [credentials](), [gcp](), [internal-tools](), [kubernetes](), [orchestration]() ### AI overview An account of building a k0s cluster for internal tooling on GCP and integrating the GCP cloud controller manager. It covers provider IDs, node reconciliation, credential scoping, load balancers, and the practical lessons learned while configuring the cluster. ### Source excerpt Why I picked k0s for an internal utility cluster, and what wiring the GCP cloud controller manager into it actually involved. ## 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 [Next page]()