Changelog

🥧 Small Tools, Better Workflows: Pie.host Weekly Update

This week at Pie.host, we added two new developer tools and shipped backend improvements to keep things running smoothly.

The goal is simple: give developers useful utilities for everyday tasks while continuing to improve the infrastructure behind Pie.host. Here’s what’s new.

🖼️ App Icon Sizer

Creating app icons for different platforms can be tedious. Each platform and device may require specific icon dimensions, and resizing images manually takes time.

Our new App Icon Sizer helps simplify this process by giving developers a dedicated tool for preparing app icons at the sizes they need.

Why it matters: Developers can spend less time handling repetitive image preparation and more time building their applications.

Example use case: You’re preparing icons for a new mobile app and need multiple sizes from a single source image. Use the tool to help prepare the required assets.

🧪 JSON Mock API Generator

Frontend development often depends on backend APIs that aren't ready yet. Waiting for an endpoint to become available can slow down UI development, testing, and prototyping.

The new JSON Mock API Generator helps developers generate mock API data using JSON, making it easier to work with sample responses during development.

Why it matters: You can develop and test frontend components without depending entirely on a production backend or a completed API.

Example use case: You're building a dashboard that displays user profiles, orders, or product information. Generate sample JSON data to test layouts, loading states, and data rendering while the actual API is still being developed.

⚙️ Backend Improvements

Alongside the new tools, we shipped backend improvements across Pie.host.

These changes focus on the systems supporting our platform, helping us maintain and improve the experience as developers use our tools and services.

We haven't introduced a major new infrastructure feature this week, but ongoing backend work remains an important part of keeping the platform reliable.

Try the new utilities, we will see you with another update, next Tuesday!

Another Tuesday, another Pie.host update!

🤖 Meet the Pie.host MCP Server: Your Cloud, Connected to AI

This week, we're making Pie.host easier to interact with through AI. We've shipped the Pie.host MCP server, allowing users to connect their Pie.host infrastructure with ChatGPT, Claude, and other MCP-compatible AI agents.

Instead of opening dashboards and navigating through different resources to find information, you can ask questions in natural language and get answers directly in your AI conversation. The goal is simple: make cloud infrastructure easier to inspect using the tools developers already work with.

🤖 Connect Pie.host to Your AI Assistant

The new MCP server brings Pie.host tools into your AI workflow through the Model Context Protocol (MCP).

Once connected, you can ask questions like:

"Hey Chat, how many PieSocket connections are active?"

You can also ask your AI assistant to look up information about your Pie.host resources without manually navigating the dashboard.

This is useful when debugging an issue, checking resource usage, or investigating your infrastructure and you want answers without switching between multiple interfaces.

☁️ Ask Questions About Your Infrastructure

The biggest benefit of this integration is the ability to interact with your cloud infrastructure conversationally.

For example, a developer investigating a realtime application could ask their AI assistant about PieSocket connections. Someone working on a deployment could use the integration to look up relevant resource information.

Instead of remembering dashboard locations or manually searching for data, you can describe what you want to know in plain English.

The AI assistant can use the tools exposed by Pie.host's MCP server to retrieve relevant information, subject to the available tools and configured permissions.

🔌 Connect ChatGPT and Claude

We've also published dedicated integration guides to help you get started with your preferred AI assistant.

• ChatGPT Integration Guide: Follow the steps to connect Pie.host with ChatGPT and start interacting with your infrastructure through conversation.
• Claude Integration Guide: Learn how to configure the integration with Claude and bring Pie.host tools into your AI workflow.

For the complete MCP server documentation, including setup details, visit the Pie.host MCP Server Guide.

🚀 Built for AI-Powered Development

MCP provides a standardized way for AI applications to interact with external tools and services. Developers can bring Pie.host into their existing AI workflows rather than building a separate, custom integration for every assistant.

As AI-powered development tools become a bigger part of everyday engineering, we want Pie.host infrastructure to fit naturally into those workflows.

We're continuing to make Pie.host more accessible to developers, whether they prefer dashboards, APIs, or AI-powered workflows.

Open a support ticket to suggest new capabilities to add to the MCP server

PS: We have reduced the free plan's daily quota of messages to 100k/day, connections limit remains 200.

Another Tuesday, another Pie.host update!
 

🌎 A More Detailed PieSocket Dashboard

The PieSocket dashboard now includes a world map showing active connections by location.

You can see where connections to your cluster are coming from at a glance, making it easier to understand your traffic distribution and identify where your users are connecting from.

We also expanded the dashboard's message analytics.

Previously, the dashboard showed a graph for total messages. It now separately tracks:

• 📤 Messages sent
• 📬 Messages delivered
• 📊 API publishes

This gives you more visibility into the flow of messages through your infrastructure instead of looking at a single aggregate number.

With the new API publish count graph, so you can see how frequently your applications are publishing messages through the PieSocket API.

🚀 REST API: Pagination for V4 Members

The PieSocket REST API can now paginate the list of members for the V4 protocol.

This is particularly useful for applications with larger numbers of members, where returning the entire list in a single API response isn't practical.

Pagination is opt-in, so existing integrations continue working as they do today. To enable it, send:

pagination=1

in the query parameters.

📚 PieSocket REST API documentation

🔌 Kick Members Through the API

We've also added APIs to close active member connections.

You can now kick:

• 👤 A single member
• 👥 All members

This is useful for operational scenarios where an active connection needs to be terminated immediately.

For example, if you rotate an API key, you may want to disconnect existing connections before allowing clients to reconnect with the new credentials. Similarly, if a user is banned, you can close their existing connection instead of waiting for it to disconnect naturally.

🛠️ Small Improvements

This week's changes are mainly focused on better visibility and operational control for PieSocket deployments, with the dashboard and REST API now providing more information and control over active connections.

Try the updated PieSocket dashboard and REST APIs to get more visibility and control over your realtime infrastructure.

Another Tuesday, another Pie.host update!

Here is what's new

🔐 Phone Verification & Two-Factor Authentication

We’ve introduced a new security requirement for all Pie.host accounts. Users must now verify their account with a phone number and enable two-factor authentication (2FA) before creating new resources.

This adds an extra layer of protection to accounts and helps secure newly created infrastructure.

What this means for existing users:

• New resources can only be created after completing phone verification and enabling 2FA.
• Existing resources continue working as usual, without interruption.

For example, if you’re already running applications or monitoring websites on Pie.host, your existing resources will continue to operate even if you haven’t completed the new verification process.

🛠️ Three New Developer Tools

We’ve added three tools to help developers work with JSON Web Tokens and SHA-1 hashes directly from their browsers.

JWT Decoder

Decode JSON Web Tokens to inspect their headers and payloads.

Useful for debugging authentication flows and inspecting token claims.

Open JWT Decoder 

JWT Encoder

Create JSON Web Tokens from a header, payload, and signing configuration.

Useful for testing token-based authentication and integration workflows.

Open JWT Encoder 

SHA-1 Generator

Generate SHA-1 hashes from input text.

Useful for development and testing workflows that require SHA-1 hashing.

Open SHA-1 Generator 

✨ Security and UI Improvements

We’ve also shipped additional security improvements and user interface refinements across Pie.host.

These updates focus on improving the overall platform experience and making it easier for developers to manage their resources.

🚀 What's Next?

We’ll continue improving account security, expanding our developer tools, and refining the Pie.host experience. Try the new tools and explore the latest updates at Pie.host 

See you next Tuesday!

Another Tuesday, another Pie.host update!

This week, we shipped a major update to PieSocket: Protocol V4 is now available.

The biggest change is how rooms are handled. With V4, a single WebSocket connection can now subscribe to multiple rooms. This can reduce the number of WebSocket connections your application needs to maintain, which can also help reduce connection usage on your PieSocket plan.

We also expanded the documentation with new guides covering V3, V4, Webhooks, and building PieSocket clients in other programming languages.

🔌 Subscribe to Multiple Rooms with One Connection

PieSocket Protocol V4 now allows a single WebSocket connection to subscribe to multiple rooms.

Previously, applications that needed to listen to several rooms could require multiple WebSocket connections. With V4, those room subscriptions can be handled through a single connection.

Fewer connections can mean lower connection usage and simpler realtime architecture, particularly for applications where users need to listen to many channels at once.

SDKs have been published for Android, Flutter, JS/React native and iOS.

Here is the 👉 quick migration guide.

📚 New PieSocket Documentation

Alongside V4, we've added several new documentation pages to make working with PieSocket easier.

🪝 Webhooks

A new guide covering PieSocket Webhooks and how to integrate them into your application.

📖 V3 Protocol Guide

We've added a dedicated reference for the existing V3 protocol, making it easier to understand and maintain applications that haven't migrated yet.

⚡ V4 Protocol Guide

The new V4 protocol now has its own documentation covering the updated connection and room subscription model.

🛠️ Build Your Own PieSocket Client

You can now build a PieSocket client in virtually any programming language by implementing the protocol yourself.

This is useful if you're working with a language that doesn't have an official PieSocket client or if you need a custom implementation for your application.

🔧 Small Improvements

This week's release also included documentation updates and cleanup around the PieSocket protocol to make the transition between versions easier.

🎯 What's Next

With Protocol V4 now released, we are soon going to publish demos and tutorials on how to integrate PieSocket, with code examples.

See you next Tuesday!