Fred and Puka represent a new wave of connected companions designed for hybrid work and play. Their modular design and responsive software help teams stay aligned while preserving individual productivity.
Built on open standards and privacy-first principles, Fred and Puka integrate scheduling, notifications, and context sharing into a single lightweight interface.
| Name | Core Focus | Deployment Model | Security Certification | Typical Use Case |
|---|---|---|---|---|
| Fred | Workflow orchestration | Cloud and on-prem | ISO 27001, SOC 2 | Automating cross-team processes |
| Puka | Real-time collaboration | SaaS-first, extensible APIs | GDPR, HIPAA-ready | Shared dashboards and alerts |
Getting Started with Fred
Fred offers guided onboarding so teams can map existing tools and define guardrails. From calendar sync to custom webhooks, configuration is visual and version controlled.
Installation and initial setup
Admins can deploy Fred in minutes via cloud marketplace or container images, with role-based access and SSO already integrated.
Productivity with Puka
Puka emphasizes rapid context switching, combining chat, metrics, and task lists into dynamic rooms. Teams use it to coordinate incident response without leaving the channel.
Live notifications and threads
Smart aggregation reduces noise, while threaded replies keep decisions traceable and searchable for future audits.
Integration and Extensibility
Both platforms expose REST and GraphQL endpoints, enabling deep links into ticketing, code repos, and knowledge bases. Web templates allow custom panels without leaving the workspace.
Developer experience and SDKs
Official SDKs for JavaScript and Python make it simple to build connectors, validate payloads, and run local tests before promotion to production.
Security and Compliance
End-to-end encryption, field-level redaction, and immutable audit logs ensure regulated data remains protected. Policy templates help map controls to internal risk frameworks.
Governance and data residency
Region-aware storage choices, export tooling, and scheduled retention policies give legal and security teams clear boundaries and verifiable reports.
Roadmap and Evolution
Upcoming enhancements focus on predictive alerts, AI-assisted summaries, and tighter governance for multi-cloud environments. Feedback channels ensure roadmap priorities reflect real team workflows.
- Evaluate Fred for centralized workflow governance and automation
- Use Puka as the real-time collaboration surface for teams and incidents
- Enable SSO and role mapping early to streamline access control
- Instrument webhooks and audit logging before scaling to production
- Review pricing tiers as usage patterns stabilize to optimize cost
FAQ
Reader questions
How does Fred handle cross-platform approvals?
Fred routes approval requests through configurable chains, allowing sequential or parallel reviews with timeouts and audit trails tied to identity providers.
Can Puka replace dedicated incident channels?
Organizations often use Puka as the primary incident hub, with Fred automating escalation, evidence collection, and postmortem creation based on event streams.
What happens when connectivity is lost on Puka?
Local queues preserve messages and actions, and once connectivity returns, delta synchronization reconciles state without duplication.
How are pricing tiers structured across Fred and Puka?
Pricing is typically per active user, with feature-based tiers that unlock advanced automation, higher retention, and dedicated support as scale increases.