RocketGoGo
Transactional messaging platform product, platform & brand
/ Overview
RocketGoGo is FGX’s transactional messaging product. The project covers product strategy, engineering, branding, the marketing site and the developer interface. Channel availability depends on provider and workspace setup.
/ Project Details
Name: RocketGoGo - transactional messaging platform
Client: FGX Studios - in-house product
Industries: SaaS & developer tools
Scope: Product, platform, brand & build
Live: rocketgogo.com
// one event, every channelawait rg.events.send({ event: "order.payment_received", order_id: "#1048", amount: "R1,250.00", channels: ["email", "sms", "wa"]})// → { id: "msg_9f2c…", status: "accepted" }
$ npm i @rocketgogo/node
• Check the current SDK documentation
✓ Confirm email API and SMTP setup
! Confirm SMS provider configuration
! WhatsApp requires account + approved template
> Illustrative checklist, not a live test
Feature availability depends on workspace setup
api key rgg_live_a3f9… issued
Email for detail. SMS for now. WhatsApp for familiar.
Illustrative message scenarios only. Shared account, API-key and wallet behaviour depends on the live workspace and has not been verified here.
/ Challenge
Every application has to send messages, and most teams end up stitching together one provider for email, another for SMS and a third for WhatsApp, each with its own credentials, templates, logs and bills. The challenge was to make transactional messaging one decision instead of three integrations, and to help developers understand the product quickly.
/ Provided Services
Product strategy
The product strategy brings transactional messaging into a shared developer workflow. Account configuration and enabled providers determine which channels can be used.
Platform engineering
API and interface work for message submission, status reporting and delivery logs. Available features and channels depend on the configured workspace.
Brand & interface
An identity built around a rocket in orbit, a deep violet palette and code-first typography, carried from the marketing site into the dashboard and the docs.
| TIME | CHANNEL | RECIPIENT | STATUS |
|---|---|---|---|
| 09:17:40 | SMS | +1 213•••8847 | delivered |
| 09:17:39 | o•••@northwind.co | sent | |
| 09:17:38 | j•••@acme.dev | delivered | |
| 09:17:37 | SMS | +27 82•••2198 | delivered |
| 09:17:36 | +27 82•••2198 | read | |
| 09:17:35 | m•••@praxis.app | delivered | |
| 09:17:34 | SMS | +44 77•••5520 | delivered |
A domain setup workflow.
Bricolage Grotesque - headlines
Inter - interface and body copy
JetBrains Mono - code, logs and data
Illustrative dashboard · sample data · not live service metrics
/ Solution
We shaped RocketGoGo around a simple developer workflow: install the documented SDK, create a client and choose a channel enabled for the workspace. Domain authentication can connect to Cloudflare, while SMS and WhatsApp availability depends on provider setup and account requirements. The site uses product-story visuals to explain the workflow.
/ Tech stack
REST API & SMTP relay
The public developer docs provide an email REST API and authenticated SMTP quickstart. SMS and WhatsApp have API documentation, but successful live sending depends on provider and account configuration.
Node.js SDK
The public docs identify the Node.js package as @rocketgogo/node. Confirm package access and enabled channels in the target workspace before integrating; one client does not by itself confirm that every channel is live.
Cloudflare DNS
The example illustrates a domain-authentication workflow. Actual verification depends on provider support, DNS configuration and propagation.
GSAP motion
The marketing site uses scroll-driven motion to illustrate sends, routing and verification. These animations are a product-story demo, not a live event stream or proof of current service performance.
A shared messaging workflow.
Email · SMS · WhatsApp
/ Outcome
The project demonstrates FGX’s work across product strategy, engineering, branding and interface design. Check the product’s current documentation and workspace configuration before planning an integration; the examples here do not verify live channel availability or service performance.
