Frequently Asked Questions (FAQ)

General Questions

How is this service different from self-hosted RabbitMQ, Kafka, or NATS?

The main difference is simplicity and zero infrastructure management. With Togo MQ, you don't need to organize any servers, configure complex clusters, or build scaling solutions. We handle all the infrastructure, scaling, and maintenance for you.

Simply use our online endpoint and integrate it into your application - no specialized knowledge about message brokers, configurations, or server management required. Focus on building your product while we take care of the messaging infrastructure.

What types of messaging patterns does your platform support?

We support the two most common messaging patterns:

  • Publish/Subscribe (Pub/Sub) - Broadcast messages to multiple subscribers
  • Message Queues - Point-to-point message delivery

These patterns cover the majority of use cases for distributed systems, event-driven architectures, and asynchronous communication between services.

Do you provide self-hosting or hybrid deployment options?

Togo MQ is exclusively available as a fully-managed SaaS solution. This allows us to provide the best possible experience with:

  • Automatic scaling
  • Maintenance and updates
  • Security patches
  • 24/7 monitoring

We do not currently offer self-hosting or hybrid deployment options, ensuring you can focus entirely on your application without infrastructure concerns.

Is the broker based on an open-source engine (e.g., NATS, Kafka, RabbitMQ)?

Togo MQ is built on our proprietary message broker technology, optimized specifically for cloud-native SaaS delivery. While we use proven architectural patterns, our broker is not open-source and we do not provide access to the source code.

This allows us to deliver a highly optimized, secure, and managed service tailored for modern cloud applications.

Features and Capabilities

What is the maximum message size?

The current maximum message size is 50 MB per message. This generous limit supports most use cases, from small events to larger payloads like:

  • File transfers
  • Batch data processing
  • Large JSON/XML documents
  • Binary data

{info} If you need larger message sizes for your specific use case, please contact our support team at support@togomq.io.

What are the limits on queue length, number of topics, or subscribers?

We believe in building for scale, so there are no limits on:

  • ✅ Queue length (unlimited)
  • ✅ Number of topics you can create (unlimited)
  • ✅ Number of publishers (unlimited)
  • ✅ Number of subscribers (unlimited)

This allows your messaging infrastructure to grow naturally with your application without hitting arbitrary caps.

Does your broker support message persistence or in-memory delivery only?

We support both persistent and in-memory message delivery. You can choose the appropriate durability level based on your use case:

  • Persistent messages - Critical messages that must not be lost
  • In-memory delivery - High-throughput scenarios where temporary loss is acceptable

Can I use custom headers or metadata in messages?

Yes, absolutely! You can define custom metadata for your messages using key-value pairs. This allows you to add:

  • Routing information
  • Correlation IDs
  • Timestamps
  • Priority levels
  • Any other custom attributes your application needs

Example:

msg := togomq.NewMessage("orders", []byte("order-data")).
    WithVariables(map[string]string{
        "priority":    "high",
        "customer_id": "12345",
        "region":      "us-east",
    })

Is there support for delayed or scheduled messages?

Yes! We provide full support for message scheduling and delays. You can:

  • Configure message delay times
  • Set retention options
  • Schedule future processing

Use cases:

  • Retry logic with exponential backoff
  • Scheduled tasks and reminders
  • Rate limiting
  • Delayed notifications

Example:

msg := togomq.NewMessage("reminders", []byte("Send email")).
    WithPostpone(3600).     // Delay by 1 hour
    WithRetention(86400)    // Keep for 24 hours

How is message ordering guaranteed?

Message ordering is guaranteed based on publishing timestamp and message postpone options. When messages are published, they are ordered according to their timestamps, ensuring predictable delivery sequence.

Important: While this provides reliable ordering based on publication time, please note that this is not atomic FIFO (First-In-First-Out) ordering.

For most use cases, this timestamp-based ordering combined with postpone capabilities provides the right balance between performance and ordering guarantees.

Technical Details

What protocols are supported (AMQP, MQTT, STOMP, REST, WebSockets, etc.)?

Currently, we provide access through our own optimized SDK built on gRPC, which offers:

  • ✅ Exceptional performance
  • ✅ Low latency
  • ✅ Excellent developer experience
  • ✅ Efficient binary serialization
  • ✅ HTTP/2-based communication

Coming Soon: We're actively working on adding support for industry-standard protocols:

  • AMQP
  • MQTT
  • Kafka connectors
  • Additional protocol support

Do you provide SDKs or client libraries? For which programming languages?

Currently Available:

  • ✅ Go SDK - Production-ready, fully supported

Coming Soon:

  • Python
  • JavaScript/Node.js
  • Java
  • C#/.NET
  • Rust

All SDKs leverage gRPC for efficient, type-safe communication with our messaging platform.

{info} Check our Installation Guide or contact us at support@togomq.io for the latest SDK availability.

Security and Compliance

How is data encrypted (in transit and at rest)?

Security is our top priority:

In Transit:

  • ✅ All data encrypted using SSL/TLS
  • ✅ Let's Encrypt certificates
  • ✅ All connections to clusters are fully encrypted end-to-end
  • ✅ Your messages are protected from unauthorized access during transmission

Coming Soon:

  • End-to-end encryption
  • Client-side encryption options

How do I authenticate with Togo MQ?

Togo MQ uses token-based authentication:

  1. Register or log in to your account
  2. Generate an API token in your Dashboard
  3. Use the token in your SDK configuration

Example:

config := togomq.NewConfig(
    togomq.WithToken(os.Getenv("TOGOMQ_TOKEN")),
)

{danger} Keep your tokens secure! Never commit them to version control or share them publicly.

Learn more in our Authentication and Tokens guide.

Pricing and Support

Which payment providers are supported?

We currently use Stripe as our payment provider, offering:

  • ✅ Secure payment processing
  • ✅ Support for major credit cards
  • ✅ Subscription management
  • ✅ Various payment methods
  • ✅ Industry-leading security
  • ✅ Global reach

Do you offer support?

Yes, absolutely! We provide dedicated email support to help you with:

  • Technical questions
  • Integration challenges
  • Troubleshooting issues
  • Best practices guidance
  • Feature requests

Contact us: support@togomq.io

Our team is committed to ensuring your success with Togo MQ!

What is your pricing model?

Visit our pricing page to see our current plans and pricing. We offer:

  • Transparent, predictable pricing
  • Multiple tiers for different needs
  • No hidden fees
  • Pay only for what you use

Can I try Togo MQ for free?

Yes! Check our homepage for current trial options and get started today.

Coming Soon Features

We're constantly improving Togo MQ. Here's what's coming:

End-to-End Encryption

Security by default - your data stays private from source to destination.

Dedicated Clusters

Isolated, high-performance clusters for maximum reliability and control.

Protocol Connectors

Seamless integration with:

  • Kafka
  • AMQP
  • MQTT
  • Other industry-standard protocols

Still Have Questions?

Can't find the answer you're looking for? We're here to help!

{success} Ready to get started? Head over to Getting Started to begin using Togo MQ in minutes!