Weekly Rundown: Your Own Stack, One Front Door

Weekly Rundown: Your Own Stack, One Front Door

Weekly rundown — the apps added to w6w between 17 and 24 August 2026.

Most integration catalogs grow sideways — another CRM, another help desk, another marketing tool a customer asked for. This week grew in a different direction. Sixty-two apps landed, and most of them are not tools anyone buys for a department. The new apps are the ones your own platform team already operates: the error tracker, the deploy pipeline, the warehouse, the identity provider, the secrets vault.

Can I manage my own infrastructure APIs in the same place as my SaaS integrations?

Yes: in w6w an infrastructure API and a SaaS API are the same object, a declared app with a Connection behind it. Sentry, HCP Terraform, BigQuery and Auth0 import, authenticate, call and health-check through exactly the path Salesforce and Slack already use. Having first-party and third-party APIs in one view describes the default here rather than a feature somebody switches on.

Pillar one restated with a different cast reads: many APIs, one access point, one credential. The claim only sounds unremarkable until you notice where those credentials used to live. Your identity provider’s key and your customer’s CRM token sat in different systems, under different rules, watched by nobody in particular.

The week had three clusters, not sixty-two stories

Three clusters do most of the explaining, and each one is a Workflow a team can now build end to end.

An entire ELT chain arrived at once. Airbyte and Fivetran land the data, BigQuery and ClickHouse hold it, dbt Cloud models it, Looker reads it back. Those six shipped inside seventy-two hours of each other. The trigger-sync, wait-for-completion, run-transformation, publish-the-Look sequence becomes one Workflow instead of a cron job and a prayer. Each step is a Connection your team already owns, and none of them needs a new place to keep a key.

Five search and vector engines. Algolia, Meilisearch and Typesense cover the keyword side; Pinecone and Qdrant cover the vector side. Five in one week is not a coincidence. A retrieval stack in 2026 looks exactly like that, and the retrieval layer is the one teams replace most often while the code above it stays still.

Identity, access and secrets became first-class. Auth0, WorkOS, JumpCloud, 1Password and Snyk arrived together. Managing a secrets vault’s API through a platform whose own argument is credential isolation carries a real irony, and the honest footnote is that those isolation properties are unaudited — no third-party audit has been run against them. The 1Password app talks to a Connect server your team runs, and its token is scoped and stored the way any other connection’s is.

All sixty-two ship declared health checks

Every app that landed this week ships at least one declared health check, because health in w6w is a property the app publishes about itself. The sixty-two carry 150 between them, two to four each. Nobody tuned that number — the app contract produces it.

The batch is where declared health earns its keep. A dead credential on a marketing tool is an annoyance somebody finds on Monday. A dead credential on Vercel, HCP Terraform or Tailscale is a deployment that does not happen. Watching your own infrastructure and your vendors through one health model — instead of a status page for them and a dashboard for you — is the point of pillar three, and this week gives the first-party half of that sentence real weight.

You did not have to wait for us

You can import an app from a GitHub URL yourself, which is why sixty-two is a pleasant number and not the argument. An app is a published spec, pinned by content address, with no vendor in the loop and no queue to join. The catalog is a convenience rather than a moat. The useful question was never how many APIs a competitor lists — the question is whether the eight you actually depend on are declared, scoped and observable.

What the first-party pack buys you is narrower and more boring. Somebody already read the vendor’s documentation, worked out which surface is the real one, and wrote the health check that catches it going quiet.

The sixty-two, grouped by what they do

All sixty-two are listed below, grouped by what they do, and every one of them sits behind the one front door. Each entry names three real actions out of the app’s declared set, and one or two apps worth wiring it to — with a Workflow per group that is genuinely worth stealing.

Ship and run it

Deploying, hosting and the boxes underneath. Workflow to steal: merge on GitHub → queue a Terraform run → apply it → create a Vercel deployment → promote to production → post the alias to Slack. One graph, five Connections, no CI plugin that only half-supports one of them.

• Vercel — deployments, aliases, and the env vars that quietly differ between them. Ask it to Create a deployment, Promote a deployment to production, or Roll back to a deployment. Pairs with GitHub, Sentry and Slack.

• DigitalOcean — droplets, volumes and DNS — with the billing surprises made explicit. Among its actions: Create a droplet, Power a droplet, Snapshot a droplet. Good beside Grafana and Slack.

• HCP Terraform — queue the plan, apply it, read the state outputs back out. The three worth knowing: Queue a run, Apply a run, Read state outputs. Sits well next to GitHub and Vanta.

• Azure DevOps — repos, pipelines and work items, queried with WIQL. You can Run a pipeline, Create a pull request and Query work items (WIQL). Best wired to Teams and Jira.

• Gitea — Git on your own box, with the whole issue and release surface attached. Call Create a pull request, Merge a pull request, or Create a release. Pairs with Discord and Sentry.

• Gerrit — change-based review, for the teams who never left it. Reach for Search changes, Review a change or Submit a change. Good beside Slack and Jira.

• balena — fleets of Linux devices — pin a release, reboot the ones that hung. List devices, Pin or unpin a device’s release and Reboot a device are the ones you will actually wire up. Sits well next to Grafana and Slack.

• Particle — call a function on a microcontroller from a Workflow step. Comes with Call a device function, Read a device variable and Publish an event. Best wired to Airtable and Slack.

• Tailscale — the tailnet’s devices, keys and ACL policy — editable, and testable before you ship it. Its surface includes List devices, Create an auth key and Validate policy, or run ACL tests. Pairs with JumpCloud and Slack.

• LaunchDarkly — flip a flag without opening the dashboard. The actions that matter: Turn a flag on or off, Get a flag’s evaluation status, Update a flag. Good beside Sentry and Slack.

Watch it

Five ways of noticing. Workflow to steal: a Checkly check goes red → open a Statuspage incident → page the on-call through PagerDuty → when the check recovers, resolve the incident and post the duration. The interesting part is that w6w is also health-checking Checkly and Statuspage themselves.

• Sentry — the pager for code that broke, with the release that broke it. Ask it to List issues, Get an event, or Create a deploy. Sits well next to Linear and Slack.

• New Relic — NRQL over everything, plus deployment markers so a spike has a cause. Among its actions: Run an NRQL query, Record a deployment, List issues. Best wired to Vercel and PagerDuty.

• Checkly — synthetic checks that run from somewhere that isn’t your laptop. The three worth knowing: Run checks now, Get a check’s current status, Create a maintenance window. Pairs with Statuspage and Slack.

• Statuspage — the page your customers refresh when it is bad. You can Set component status, Create incident and Resolve incident. Good beside Checkly and Slack.

• Vanta — which controls are failing, and precisely which resource is failing them. Call List the entities failing a test, List vulnerabilities, or List issues. Sits well next to Jira and Slack.

Move and model the data

The whole ELT chain landed inside seventy-two hours. Workflow to steal: trigger an Airbyte sync → poll the job until it finishes → trigger the dbt Cloud job → download run_results.json → run a Look and post the number to Slack. That used to be a cron job and a prayer.

• Airbyte — trigger the sync and actually watch the job, rather than hoping. Reach for Trigger a sync, Get a job or Pause or resume a connection. Best wired to BigQuery and dbt Cloud.

• Fivetran — the same job with managed connectors, plus dbt transformations. Sync a connection, Run a transformation and Run a connection’s setup tests are the ones you will actually wire up. Pairs with Snowflake and Looker.

• dbt Cloud — run the models, then download the artifacts that prove they ran. Comes with Trigger a job run, Get a run and Download a run artifact. Good beside Airbyte and Slack.

• BigQuery — SQL, streaming inserts, and jobs you can poll to completion. Its surface includes Run a query, Stream rows into a table and Get query results. Sits well next to Google Sheets and Looker.

• ClickHouse — fast SQL — and the control plane to scale the service under it. The actions that matter: Run a query, Insert rows, Scale a service. Best wired to Grafana and Airbyte.

• Looker — run a Look and hand the numbers to something that isn’t a dashboard. Ask it to Run a Look, Run a query, or List dashboards. Pairs with Google Sheets and Slack.

• MongoDB Atlas — the control plane — clusters, database users, IP lists. Deliberately not the data. Among its actions: Create a cluster, Create or update a database user, Add an IP access entry. Good beside HCP Terraform and PagerDuty.

Search and vectors

Five engines in one week, which is what a retrieval stack looks like now. Workflow to steal: a Sanity document is published → chunk it → embed it → upsert into Pinecone → and write the same record into Algolia, so keyword and semantic search never drift apart.

• Algolia — records, synonyms and rules, kept in step with wherever the truth lives. The three worth knowing: Search an index, Batch write records, Save a synonym. Sits well next to Sanity and Shopify.

• Meilisearch — search on a box you run, with index settings you can version. You can Search, Add or update documents and Update index settings. Best wired to Supabase and Notion.

• Typesense — same idea, with scoped API keys and several searches in one call. Call Search a collection, Import documents, or Create an API key. Pairs with Airtable and WordPress.

• Pinecone — upsert, query by vector, and rerank without standing up a second service. Reach for Upsert vectors, Search by text or Rerank documents. Good beside OpenAI and Anthropic.

• Qdrant — collections, filters, payload indexes and snapshots — the whole surface. Upsert points, Query points and Create a snapshot are the ones you will actually wire up. Sits well next to Hugging Face and OpenAI.

Identity, access and secrets

The cluster with the most irony in it. Workflow to steal: a new hire lands in Gusto → create the JumpCloud user → add them to the right groups → invite them to the WorkOS organization → issue a Tailscale auth key → post the checklist to Slack. Offboarding is the same graph, reversed.

• Auth0 — users, roles, organizations, and the tenant log behind them. Comes with Search users, Assign roles to a user and Create a password-change ticket. Best wired to HubSpot and Slack.

• WorkOS — single sign-on connections, Directory Sync, and an Admin Portal link you can send. Its surface includes List directory users, Create an Admin Portal link and Invite a user to an organization. Pairs with Salesforce and Slack.

• JumpCloud — one directory for the users and the laptops they keep losing. The actions that matter: Create a user, Run a command, Lock, restart or shut down a device. Good beside BambooHR and Slack.

• 1Password — read one field out of a vault, through a Connect server you run. Ask it to Get one field’s value, List items, or List audit events. Sits well next to HCP Terraform and Slack.

• Snyk — issues, targets, and an SBOM per project when counsel asks. Among its actions: List issues, Get a project’s SBOM, List a group’s issues. Best wired to Jira and GitHub.

Product analytics

Workflow to steal: Stripe reports a churned subscription → query the retention curve for that cohort in Amplitude → pull the account’s last session from Mixpanel → drop the whole picture into the CRM before anyone dials.

• Amplitude — send the event, then ask the funnel what happened to it. The three worth knowing: Track events, Query a funnel, Query retention. Pairs with Segment and Slack.

• Mixpanel — import events, query cohorts, export the raw stream when you must. You can Import events, Query a saved report and Export raw events. Good beside Segment and BigQuery.

• Google Analytics — GA4 reports, realtime included, without opening the UI. Call Run a report, Run a realtime report, or Create a key event. Sits well next to Google Sheets and Looker.

AI and media

Workflow to steal: a Mux asset finishes encoding → Deepgram transcribes it → the transcript is embedded and upserted into Qdrant → the thumbnail is transformed by Cloudinary → the whole thing is filed in Notion. Five vendors, one graph, one credential each.

• Hugging Face — search the Hub, read dataset rows, run chat through the router. Reach for Search models, Read dataset rows or Run a chat completion. Best wired to Qdrant and Replicate.

• Replicate — start a prediction, wait for it, put the output somewhere useful. Run a model, Get a prediction and Start a training are the ones you will actually wire up. Pairs with Cloudinary and S3.

• Deepgram — transcribe by URL, then analyse what was actually said. Comes with Transcribe audio from a URL, Analyse text and Generate speech from text. Good beside Mux and Notion.

• Mux — assets from a URL, live streams, and the viewer metrics afterwards. Its surface includes Create asset from a URL, Create a live stream and List video views. Sits well next to Cloudinary and Deepgram.

• Cloudinary — upload, tag, transform, and build the delivery URL at the end. The actions that matter: Upload asset, Apply transformations or analysis to an existing asset, Build a delivery URL. Best wired to Shopify and Webflow.

Object storage

Workflow to steal: a Replicate model finishes → write the output to Cloud Storage → mint a V4 signed URL that expires → email it with Resend. The bytes never pass through anything that keeps them.

• Azure Blob Storage — containers, blobs and tiers — plus SAS URLs minted from the account key. Ask it to Upload a blob, Download a blob, or Change a blob’s tier. Pairs with Azure DevOps and Snowflake.

• Google Cloud Storage — buckets and objects, with V4 signed URLs minted offline from the key. Among its actions: Upload an object, Create a signed URL, Compose objects. Good beside BigQuery and Replicate.

Content and documents

Workflow to steal: a Storyblok story is published → Vercel redeploys → the record is pushed into Algolia → a Confluence page logs what shipped. Or the contract version: send a Documenso envelope, wait for the signature, file the audit trail.

• Sanity — GROQ in, transactional mutations out, with revisions you can read back. The three worth knowing: Query documents (GROQ), Patch document, Publish document. Sits well next to Algolia and Cloudinary.

• Storyblok — stories, drafts, and the publish button as an API call. You can Create a story, Publish or unpublish a story and Search stories (management). Best wired to Vercel and Cloudinary.

• NocoDB — a spreadsheet that is honestly a database, with links you can follow. Call Create records, List linked records, or Update records. Pairs with Airtable and Slack.

• Confluence — pages, spaces and CQL search, for the wiki that will outlive everyone. Reach for Create a page, Search content (CQL) or Add a comment. Good beside Jira and Slack.

• Miro — sticky notes, connectors and frames, created by machine for once. Create a sticky note, Create items in bulk and Create a connector are the ones you will actually wire up. Sits well next to Jira and Notion.

• Documenso — signature envelopes with an audit trail you can actually read back. Comes with Send an envelope for signature, Read an envelope’s audit trail and Create an envelope from a template. Best wired to HubSpot and Slack.

• Dropbox Sign — templates, reminders, and the file once it is finally signed. Its surface includes Send a signature request from a template, Send a reminder and Get a signature request’s files. Pairs with Salesforce and Box.

People and money

Workflow to steal: an Ashby offer is accepted → create the Gusto employee → open the JumpCloud account → file the Deel contract → and only then tell Slack. The bit that usually breaks is step four, because it lives in a different tab.

• Deel — contracts, people, time off, and the invoice adjustments nobody enjoys. The actions that matter: List contracts, Request time off, Create an invoice adjustment. Good beside QuickBooks and Slack.

• Gusto — payroll, employees, pay schedules and departments. Ask it to List payrolls, Create employee, or List time off requests. Sits well next to BambooHR and Xero.

• Ashby — move an application to a stage, and read the feedback behind the move. Among its actions: Move an application to a stage, Search candidates, List interview feedback. Best wired to Notion and Slack.

• Lever — opportunities through the pipeline, with the notes attached. The three worth knowing: Move an opportunity to a stage, Create an opportunity, Add a note. Pairs with Google Sheets and Slack.

• Plaid — balances, transactions and identity — plus the Items holding them together. You can Sync transactions, Get live balance and Get account holder identity. Good beside Stripe and QuickBooks.

Talking to people

Workflow to steal: a Stripe payment fails → Loops sends the dunning sequence → if it is still unpaid after five days, open a Front conversation and assign it to a human. The escalation is a branch, not a separate tool.

• Resend — transactional email, domain verification, and broadcasts to an audience. Call Send an email, Verify a domain, or Send a broadcast. Sits well next to Stripe and Supabase.

• Loops — events in, lifecycle email out. Reach for Send a transactional email, Send an event or Create or update a contact. Best wired to Stripe and PostHog.

• Front — a shared inbox you can assign, tag and reply to from code. Reply to conversation, Assign conversation and Search conversations are the ones you will actually wire up. Pairs with HubSpot and Linear.

• Bluesky — posts with rich-text facets built correctly, on any AT Protocol PDS. Comes with Create a post, Search posts and Get the timeline. Good beside Mastodon and Buffer.

• Mastodon — any instance you like — each one its own API, with its own limits and rules. Its surface includes Post a status, Search and Get the home timeline. Sits well next to Bluesky and Discord.

And three that fit nowhere

Workflow to steal: a WooCommerce order arrives → Google Maps validates the shipping address → EasyPost rates it across carriers and buys the cheapest label → the tracking number goes back to the customer. Home Assistant is not part of that one, and we are fine with it.

• EasyPost — rate it across carriers, buy the label, track it to the door. The actions that matter: Create a shipment and get rates, Buy postage for a shipment, Track a parcel. Best wired to Shopify and WooCommerce.

• Google Maps Platform — geocode, validate, route, and snap a GPS trace back onto roads. Ask it to Geocode an address, Validate an address, or Compute a route matrix. Pairs with HubSpot and Airtable.

• Home Assistant — call a service in your actual house from a Workflow step. Yes, really. Among its actions: Call a service, Get an entity’s state, Turn entities on or off. Good beside Telegram and Particle.

That is one week of the catalog: 62 apps, 1,185 actions and 150 declared health checks. Next week’s rundown picks up where this window closed. Browse the first-party app catalog in the meantime, or read the app contract if you would rather declare your own API.