A Rich Communication Services network operated by OzarksMade, built on the same published GSMA and IETF standards that carrier RCS runs on. It carries chat for Messages by OzarksMade, with end-to-end encryption, cloud synchronization across your devices and continuity to a tablet or second phone. Free of charge through December 31, 2026.
Rich Communication Services is the industry successor to SMS and MMS. It is defined by the GSMA, implemented by mobile network operators, and carried by an IMS core. OzarksMade RCS is an implementation of that standard operated as a service.
Chat features on Galaxy devices have always been delivered over somebody else's network. For roughly seven years, Samsung Messages carried Chat features over Google's Jibe infrastructure. Samsung did not operate an RCS network, and neither did most handset manufacturers. Access to RCS has been controlled by a small number of platform owners and carriers, and an application without that access has had no route to modern messaging.
OzarksMade RCS removes that dependency. Provisioning, registration, session handling, message transport, delivery notification and media transfer are all operated by OzarksMade. Messages by OzarksMade connects to it directly. No third-party messaging application is required on the device, and no second inbox is created.
It is the real protocol, not an approximation of it. The network speaks GSMA autoconfiguration over HTTPS, SIP over TLS, CPIM message envelopes, IMDN delivery and read notifications, and MSRP and FT HTTP for media. A conformant RCS client written against the published specifications can connect to it, which is the test that distinguishes a standards implementation from a proprietary service with a familiar name.
They are separate networks. A chat sent on OzarksMade RCS reaches another person on OzarksMade RCS. When the person you are messaging is somewhere else, the app sends a text or picture message instead, which arrives normally and costs nothing extra. Nothing is lost and nothing fails to deliver, but read receipts, typing indicators, full-quality media, real group chats and end-to-end encryption all need both people on the same network.
Interconnection is something we want, and nothing more than that today. RCS is a published GSMA standard and interconnection between networks is part of it, which is what makes this possible in principle. We intend to pursue it. No agreement exists, no timeline exists, and nothing here should be read as a commitment.
Which means the network is worth what its members make it worth. The single most useful thing anyone can do with this app is hand it to the people they message every day. Three is enough to change how your inbox feels.
Everyone else still hears from you. Text and picture messaging is included with the application, always on, and never charged by OzarksMade. Nobody is unreachable because they have not installed anything.
Every layer of the network implements a document that anyone can read. The specifications below are the ones the implementation is written against and tested to.
| Layer | Specification | What it governs |
|---|---|---|
| Service definition | GSMA RCC.71 Universal Profile | The feature set an RCS client and network are expected to provide, and the version negotiated between them. |
| Provisioning | GSMA RCC.14 | Autoconfiguration over HTTPS, including the mobile-originated SMS procedure used to establish which subscriber number a device holds. |
| Client behaviour | GSMA RCC.07 | Registration, capability discovery, one-to-one and group chat, file transfer, and the chatbot interface. |
| Signalling | IETF RFC 3261 | SIP registration, sessions, transactions and message routing. |
| Authentication | IETF RFC 7616, RFC 8760 | Digest authentication of every registration and request. |
| Message envelope | IETF RFC 3862 | CPIM, which carries the sender, recipient, timestamp and content of every message. |
| Receipts | IETF RFC 5438 | IMDN delivery and read notifications. |
| Composing state | IETF RFC 3994 | The typing indicator, including the interval after which it expires. |
| Media session | IETF RFC 4975 | MSRP, for content carried inside a session. |
| Message store | OMA CPM | Server-side message history and its synchronization to a device. |
Conformance is a design constraint, not a claim. Where the specification prescribes a behaviour, the implementation follows it even when a simpler approach would work in practice. The mobile-originated verification procedure, the transaction timers, the compact header forms, the framing of a message on a stream, and the rules for which party may authorize a presence subscription are all taken from the documents above rather than invented.
What the network provides, expressed through the One UI design Messages by OzarksMade already uses.
Messages are delivered over the chat session rather than as text messages, without length limits, without splitting, and without the cost of a multimedia message. Group conversations carry a real participant list, a subject and an icon, and adding or removing a participant is a network operation rather than a new thread.
Each message carries a delivery notification when it reaches the recipient's device and a read notification when it is opened, as defined by IMDN. Notifications are per message and per participant, so a group conversation reports who has seen what.
The composing state is published while a person is writing and expires on its own if they stop, so an indicator cannot be left showing after the fact.
Content is uploaded to the content server and delivered as a reference, rather than being recompressed into a multimedia message. Recipients receive the file at the resolution it was sent.
A message can be reacted to, edited after sending, or recalled. Each is carried as a reference to the original message, so a client that does not support them shows a readable fallback rather than nothing.
A message addressed to a device that is offline is held by the network and delivered when that device registers again, rather than failing at the sender.
One-to-one and group chats are encrypted between the people in them, using the MLS mechanism the RCS standard defines. The keys belong to the devices in the conversation. The network moves the messages and cannot read them, and neither can we.
A business on the network has a registered name, logo and brand colour, and a verified mark a person can check before trusting what it sends. The profile is shown before the conversation starts, not after.
Rich Communication Services defines how messages travel. It does not define what happens to a person's history, or how their devices stay in step. Three OzarksMade services cover that ground. Each authenticates with a credential issued for a verified phone number, and none of them requires chat features to be switched on.
Conversation history is stored in the cloud message store and synchronized to the device incrementally. A new phone restores the conversations that were on the old one, and a message read on one device is read on the others. Text messages and multimedia messages are included, not only chat.
A tablet or a second phone is paired to the primary device and can send and receive using the primary device's number. A dual-SIM phone can share either number or both, and the choice can be changed at any time without repairing.
Whether a contact is currently in the application, and whether they are in the conversation with you. The person being observed authorizes who may see it, and the service is only ever able to answer with respect to the person asking.
All three depend on proof that the device holds the number it claims. That proof is established by the device sending a message from its own subscriber identity, as the provisioning specification describes, and it happens without the user being asked to type anything.
An open network is not an unguarded one. Access is controlled at three separate points, and each answers a different question.
Transport. Signalling is carried over TLS only. The network does not offer an unencrypted signalling port and a client is not permitted to negotiate down to one.
Subscriber. Every registration is authenticated with Digest, against a credential issued only after the subscriber number has been proven. A credential is bound to one number, and a device holding a credential for one line cannot act as another.
Application. A client presents evidence of what it is, not only who it acts for. That evidence combines platform attestation, a client certificate issued by the OzarksMade certificate authority, and a signature over the registration itself. The mechanism is the one the provisioning specification describes for exactly this purpose, and it is what allows the network to be opened to third-party clients without opening it to anything at all.
Rate and scope. Endpoints that send messages, publish presence or issue credentials are bounded per device and per subscriber number, so a single misbehaving installation cannot spend the capacity that belongs to everyone else.
RCS is an open standard, but carrier provisioning servers accept only clients that have been onboarded, and there is no public application process. OzarksMade RCS accepts them.
An application can provision and register its own users' phone numbers and exchange messages on the network. It is written against the published specifications rather than a proprietary interface, which means the same implementation answers to any operator that implements the same documents.
A Rich Business Messaging agent holds an addressable identity on the network, with a brand profile a person sees before they choose to trust it. Agents support rich cards, carousels, suggested replies and suggested actions, as defined by the chatbot interface in the client specification.
The platform deliberately does not provide a simplified interface for sending a message. An application written against a convenience layer becomes a client of that layer. An application written against provisioning, registration and CPIM is an RCS client, and remains one.
The documentation, the developer portal, the sample applications and the onboarding process are in internal development and are not published. There is nothing to sign up for today. Contact us and we will tell you when there is.
Chat features and Sync with OzarksMade Cloud are provided free of charge through December 31, 2026. The period covers testing and early adoption, and no charge applies without notice beforehand.
From January 1, 2027, each service is a separate monthly subscription. Chat features are $0.99 per month and cover the conversation experience on the OzarksMade RCS network: delivery and read notification, typing indicators, full-quality photos and video, group chats and end-to-end encryption. Sync with OzarksMade Cloud is $4.99 per month and covers synchronization across a person's devices, secure storage of messages and restoration onto a new device. The two are independent and either may be held alone.
One chat features subscription covers two phone numbers. A device with two SIM cards is a single subscriber with two lines, and is charged once.
Text messages and multimedia messages are never charged by OzarksMade. They are carried by the mobile network and are included with the application, which is a one-time purchase on Google Play. Subscriptions are billed by Google Play, may be cancelled at any time from the Play Store, and the application contains no advertising.
OzarksMade RCS is rolling out now. The network is operating and beta testers are on it. Production follows within days, and this page is updated as each stage opens.
Companion Mode is being retired. Google changed the requirements for pairing with Google Messages in a way OzarksMade is not prepared to meet on behalf of its users; the reasoning is set out in the service notice. OzarksMade RCS replaces it. No action is required and nothing on your phone is deleted.
Text messages and multimedia messages are unaffected. They are carried by the mobile network, they are included with the application, and they are never charged separately. Nothing described here changes how the application handles the messaging a person relies on now.
The developer program has not opened. The documentation, the developer portal, the sample applications and the onboarding process are in internal development. Nothing is published and there is no application process yet.