Docs / Contact / overview

Tendrl: Contact + Strand

Build connected products without building heavy platform plumbing.

Tendrl combines Contact (entity + messaging infrastructure) and Strand (workflow orchestration) so teams can move from event to action in minutes.

Start with Contact

Why teams pick Tendrl

• Fast setup: register entities, issue API keys, and start sending data right away
• One model for data flow: ingest with Contact, automate with Strand
• Built-in guardrails: validation, IAM roles/policies, and encrypted credentials
• Operational visibility: message history, flow traces, and run-level debugging
• Scale on your timeline: start small and grow capacity as usage increases

Contact: Connectivity made simple

Contact gives you a clean way to manage entities and move messages through your system.

• Entity management for devices, services, and grouped assets
• MQTT + REST ingestion paths for real-time and service-driven traffic
• Validation rules to reject malformed payloads before they propagate
• Alerts for offline devices and threshold breaches, delivered in-app or through a connector
• Flow integration to route messages into connectors and automations
• Insights for usage, health trends, and delivery behavior
• SDK support across Python, Go, JavaScript, and MicroPython-style environments

Learn more in Entities, Messages, SDKs & Clients, and the API Reference.

Strand: Automation without complexity

Strand is a visual, event-driven workflow engine built for practical integrations.

• Drag-and-drop workflow editor for fast orchestration
• Node-based execution with branching, loops, and reusable flow calls
• Connectors across cloud, messaging, HTTP, AI, and internal systems
• Templating with Jinja2 + JSONPath for robust data transformation
• Scheduled + triggered workflows for both recurring and real-time operations
• Run history and step traces to debug exactly what happened

Together, Contact and Strand let you move from incoming signal to business action with less code and fewer moving parts.

A simple model

1. Connect entities and services with Contact
2. Validate data at ingestion boundaries
3. Orchestrate workflows in Strand
4. Observe every message and run
5. Iterate quickly as your use case grows

Explore next

• Quick Start
• Create your first entity
• Send your first message
• Alerts: get told when a device drops offline or a reading crosses a threshold
• Flows: the record of where each routed message went, alerts included
• Access Control (IAM): roles, policies, and API keys for users, entities, and keys
• Contact MCP Server: connect an AI assistant to manage entities, messages, and flows from a conversation
• Strand MCP Integration: use AI assistants to drive Strand workflows

← Back to Contact docs