relay.graphics

What it is

Relay for Figma positioned itself as a “Continuous Design Delivery” tool. Its core goal was to push graphic assets from Figma directly into a GitHub Repo, creating a link between design files and live websites. It targeted design operations, frontend collaboration, and teams that frequently update website graphics, aiming to reduce ZIP packaging, emailing assets, and repeated handoffs.

Core capabilities

Based on the page content, Relay’s key workflow was “Figma to Relay, Relay to Repo.” After making graphic changes in Figma, designers could push them to a code repository through Relay. It also highlighted one-click optimized image output, automatically compressing file sizes and reducing the amount of image processing needed before production. For exports, Relay offered a routing system that could output assets to multiple folders and export them in different sizes and formats, making it suitable for most project structures.

Collaboration and engineering workflow

Relay’s more valuable idea was making the design workflow better fit the engineering workflow. After connecting Figma, Relay, and GitHub, designers could push changes with one click, while Relay created and committed to a branch and opened a Pull Request. This meant graphic updates were no longer just design deliverables, but could enter code review and release workflows. That was especially relevant for design systems, marketing sites, product websites, and other scenarios where visual assets are updated frequently.

Pricing and licensing

The page previously listed three pricing tiers: a free plan at $0/month, including the first Relay Project; a $12/month plan for side projects, supporting up to 10 Relay Projects; and a $29/month plan for freelancers, supporting unlimited Relay Projects. Team, startup, and enterprise plans were marked as coming soon. The main content did not specify payment methods, copyright ownership, asset licensing, or support terms.

Pros, cons, and who it is for

The strengths were its clear vertical positioning: connecting Figma with GitHub, and reducing friction between design and development through image compression, multi-format export, and Pull Requests. The drawbacks were also obvious: it depended heavily on Figma and GitHub, making its use case relatively narrow; team plans and later-stage workflows did not appear to have been fully launched; most importantly, the page clearly stated that “Relay has closed down,” meaning the service has been shut down and should not currently be relied on for production workflows.

Access from China and alternatives

The page did not provide information on access from mainland China, network stability, or payment options, so its accessibility status can only be considered unknown. Given that the service has closed down, more practical alternatives for teams in China would be using Figma’s native export features, GitHub Actions, self-hosted asset sync scripts, or combining tools such as Zeplin, Zeroheight, and Storybook to build a design asset management and delivery workflow.