Build from scratch
Own every layer—from delivery retries and reconnects to unread state, moderation, migrations, upgrades, and production incidents.
Maximum flexibility · Maximum effort
For marketplace and community products
Ship messagingwithout giving up control.
ChatKitty pairs a production-ready messaging core with open-source integrations, while your application-specific code stays private. Run it in infrastructure you control, or have us manage a dedicated deployment. Once scope and designs are approved, and access is in place, we deliver your first direct or group messaging workflow in 10 business days.
Launch sprints from USD 7,700One workflow in 10 business daysFinal 50% at staging acceptance
staging.chat.acme.app
Running in your cloudHealthy
ChatKitty1 Docker container
Postgres
Valkey
✓
Message delivered42 ms
↗
Webhook sentorder.message.created
Teams that have built with ChatKitty include
Selia YC W22PrivateAutoInnagoKasper
Paths to shipping messaging
Ship your product. Skip the platform build.
ChatKitty gives you a third way: a production-ready messaging core in infrastructure you control, open-source integrations, and private custom code — designed for your workflow.
Buy a chat API
Launch quickly. In return, your messaging depends on the provider’s hosting model, data handling, pricing, service limits, availability, and roadmap.
Fastest start · Least control
Customer-controlled
Deploy ChatKitty
Run ChatKitty in infrastructure you control, integrate through personalized and open-source components, and choose whether your team or ours operates it.
Control without the rebuild
What the launch sprint includes
From signed-in user to working conversation.
We integrate one direct or group messaging workflow into your existing app, deploy it to staging in infrastructure you control, and test it against agreed on written acceptance criteria.
Identity and authentication
We connect your chat implementation to the users, roles, sessions, and authorization rules your app already trusts.
Direct and group messaging
Ship one-to-one conversations, private groups, channels, membership, and message history.
Inbox and unread state
Conversation ordering, last-read tracking, unread counts, delivery state, and read receipts.
Rich messages and notifications
Attachments, notification hooks, typing state, presence, reactions, edits, and deletes where useful.
Safety and moderation
Reporting, blocking, moderator controls, and application-specific enforcement paths.
Integration documentation
Architecture notes, configuration, operational guidance, and a developer handoff your team can use.
Staging deployment
A working implementation in staging, verified against written acceptance criteria before final payment.
Launch support
Production planning, release support, and 14 days of post-launch defect correction for the agreed scope.
Deliberately simple infrastructure
One deployable service.
ChatKitty is packaged as one Docker container backed by Postgres and Redis-compatible Valkey. It runs on a standard Linux deployment.
01
Your infrastructure boundary. Run chat in a supported environment your team approves. Your cloud account, services, network rules, and data remain under your control.
02
A clear operating model. Operate chat yourself, or have us manage a dedicated, fixed-capacity deployment with responsibilities, support hours, and limits defined up front.
03
Integrate without rebuilding your app. Keep your existing interface, use our open-source integration components, or scope a new messaging experience before implementation begins.
Your cloud boundary
Your productWeb · iOS · Android
HTTPS + WebSocket
ChatKitty serviceDocker container
healthyP
PostgresDurable state
V
ValkeyRealtime state
Optional connections
↗ Push providers
↗ Object storage
↗ Your webhooks
Choose who operates it
Your cloud. You choose who runs it.
Choose the level of operational ownership that fits your team.
Your team operates
Self-managed BYOC
Run chat in a supported container environment using your own infrastructure and operating processes. We provide the Docker image, deployment configuration, integration work, migrations, and operating documentation.
- Runs on a standard Docker-capable Linux host
- Your team controls network, access, backups, and monitoring
- Support and upgrade assistance
Best for teams with existing infrastructure.
Deployment option 1Most hands-off
ChatKitty operates
Managed by ChatKitty
We operate ChatKitty for you with managed Postgres and Valkey inside the agreed deployment boundary.
- Monitoring, updates, backups, and routine maintenance
- Monthly support and an accountable technical owner
- Capacity reviews as your usage changes
Capacity note: Managed single-instance mode does not automatically scale with usage. Scaling and high availability are planned separately.
Deployment option 2The Chat Launch Sprint
Your messaging workflow, ready to launch in 10 business days.
We deploy chat and integrate one direct or group messaging workflow into your existing web app. The delivery clock starts after scope, access, designs, and technical checks are complete.
- Before kickoff01
Confirm scope and readiness
We confirm the workflow, technical fit, responsibilities, acceptance criteria, access, and operating mode before the delivery clock starts.
- Days 1–202
Establish the foundation
We confirm the architecture, deploy chat to staging, configure PostgreSQL and Valkey, and verify the environment.
- Days 3–703
Integrate the workflow
We connect authentication and identity, then implement the agreed messaging workflow, history, application states, permissions, and interfaces.
- Days 8–904
Validate in staging
We test the integration, permissions, restarts, and supported browsers, then walk through staging and resolve in-scope defects.
- Day 1005
Prepare for launch
We complete final fixes, documentation, developer handoff, and the production checklist so the agreed workflow is ready for release.
Complex integrationsLarger migrations, enterprise identity, or broader product work are typically scheduled for 15–20 business days and priced separately.
ChatKitty has played a crucial role in simplifying the development process for our in-app chat system.
Built with product teams
ChatKitty combines a proven messaging platform with direct engineering support, so the people who understand the system are accountable for the implementation.
Discuss your integrationFixed-scope launch sprint
One workflow.
One fixed price.
Once discovery is complete, we integrate one defined direct or group messaging workflow into your existing web app and take it to staging acceptance in 10 business days. Scope, responsibilities, and acceptance criteria are agreed before kickoff. Anything beyond the agreed scope is quoted separately.
Common additions, scoped separately
A second messaging workflowNative mobile integrationCustom interface redesignHistorical data migrationEnterprise SSO
ChatKitty Launch Sprint
Standard implementation
USD 7,700
For an existing web application with one defined direct or group messaging workflow. The sprint requires a supported technical environment, completed discovery, and timely access to your codebase and team.
One workflowOne application10 business days
- Technical check and architecture confirmation
- ChatKitty staging deployment in your cloud
- Authentication and user identity integration
- One direct or group messaging workflow
- Conversation list, history, unread state, and basic permissions
- Staging acceptance walkthrough
- Technical documentation, developer handoff, and production-launch support
- 14 days of post-launch defect correction
50% to reserve the sprint50% at staging acceptance
Book a technical fit callAfter launch
Operate ChatKitty independently, add optional ongoing support for USD 400/month, or have us manage your deployment from USD 950/month plus cloud costs.
Applicable taxes and separately approved work are additional. Production launch follows staging acceptance, final payment, and your approved release window.
✓ Strong fit
Built for teams ready to ship.
- Marketplace or community product with an existing user base
- Messaging planned within the next 90 days
- A product or engineering owner can make decisions quickly
- Your team can provide code, environment, and technical access on schedule
- A defined user journey and business reason for in-app messaging
× Not a fit yet
Some projects need a different first step.
- An idea without an existing product or implementation team
- No defined user journey or business reason for messaging
- A request to build the entire application within the sprint
- No access to the codebase or deployment environment
- Unlimited customization expected inside a fixed-price scope
Clear answers
Know exactly what you are buying.
ChatKitty has a defined scope, clear responsibilities, and explicit operating limits. These are the questions teams usually resolve before they commit.
Can ChatKitty run in our cloud?
Yes. In self-managed mode, ChatKitty Core runs as a versioned OCI image in a supported container environment with PostgreSQL and Valkey. Alternatively, we can manage one dedicated ChatKitty instance in our DigitalOcean account.
What do we own?
You own your cloud account, infrastructure, databases, data, application, and customer-specific integration code. ChatKitty Core remains proprietary and is licensed as a container image. The reusable ChatKitty integration layer is open source.
What can we launch in 10 business days?
After technical discovery, the standard sprint takes one agreed web messaging workflow to staging. It typically includes deployment, authentication and user mapping, direct or group messaging, conversation history, unread state, basic permissions, testing, documentation, and handoff. Production follows acceptance and your approved release window.
Can ChatKitty use our current authentication and user model?
Yes, when it fits the supported integration path. Your application remains the source of truth for users, sessions, roles, and permissions. We map that model into ChatKitty instead of introducing a second identity system.
Do we need to replace our existing chat interface?
Not necessarily. We can connect a compatible existing interface to the open integration layer or use supported ChatKitty components. A full redesign, a second client platform, or substantial custom interface work is scoped separately.
Does the standard managed service autoscale or provide high availability?
No. The standard managed service runs one fixed-capacity ChatKitty instance with business-hours operational support. We monitor health and capacity and recommend planned resizing when needed, but automatic scaling, application failover, multi-region continuity, and 24/7 response are not included.
What if our project is larger than the standard sprint?
Additional platforms, workflows, data migration, attachments, push notifications, substantial interface work, complex security requirements, and non-standard infrastructure are scoped as separate fixed-price phases. When the architecture is not yet clear enough to quote responsibly, we begin with a paid architecture session.
What support is included after launch?
The sprint includes 14 days of defect support against the agreed acceptance criteria after production launch. Ongoing service is provided through either a self-managed software subscription with releases and product support or a managed plan with updates, monitoring, capacity review, and application operations. New feature work is quoted separately.
Give chat a launch date
Find out whether the sprint fits your product.
Bring the use case, current stack, and target date. The first call is a 20-minute technical fit check.
01
Assess the fit. We confirm the user journey, urgency, technical path, and operating model.
02
Get a direct answer. You leave knowing whether the standard sprint fits or requires another scope.
03
Choose a concrete next step. Proceed to scope, paid architecture, or a clear decline.