Skip to content
Ragtime Developers

Product Updates

  • Encrypted database volumes and a rebuilt billing engine

    Ragtime Teamsecurityinfrastructurebilling

    The Ragtime database now runs on encrypted volumes, billing has been rewritten, and BYOK support is being prepared for partners and direct customers.

    August focused on the layers underneath the product. Moving to volume-level encryption removes a constraint that had been blocking work on retrieval, and the billing rewrite clears the way for bring-your-own-key deployments.

    • Encrypted database volumes — The Ragtime database now runs on encrypted volumes, so all data is encrypted at rest. This replaces the previous column-level encryption, which limited the retrieval features we could build on top of stored content. No migration is required on your side.
    • Rebuilt billing engine — Billing has been rewritten from the ground up for clearer usage accounting and more flexible plan structures. Existing plans and invoices are unchanged.
    • Groundwork for BYOK — The new billing foundation prepares support for bring-your-own-key setups, where channel partners and direct customers supply their own AI provider credentials. More details to follow as this rolls out.
    • Ongoing security updates — Continued dependency updates and hardening across the platform.

  • July platform release: security, API validation, and a rebuilt chat UI

    Ragtime Teamreleasesecurityapichat

    A large refactoring round: 30 pull requests and more than 150 fixes covering security hardening, API validation, a unified chat renderer, spreadsheet ingestion, and chat theming.

    July was a consolidation month. Over roughly six days of focused refactoring we merged 30 pull requests and resolved more than 150 issues on staging, all of which are now live. The work concentrated on closing abuse vectors, making the public API predictable and documented, and removing duplication that had built up in the chat client.

    • Security hardening — Closed four abuse gaps covering webhook signature verification, analytics authentication, tool name collisions, and unbounded input sizes. Draft assistants can no longer be reached before publication, and several localization bugs were fixed.
    • API validation and expansion — Thirteen v1 handlers moved to schema-based request validation, which surfaced and fixed five bugs. We published an OpenAPI 3.1 contract for the public API and exposed eight new analytics endpoints.
    • Chat UI refactor — Three duplicated chat renderers were unified into one. The theme system was rebuilt on OkLab colour math with eight presets, microphone pickers were consolidated into a single component, and rendering issues on iOS Safari were fixed.
    • Chat theming — Eight presets with device-aware light and dark schemes, laying the groundwork for broader visual customisation of embedded assistants.
    • Spreadsheet ingestion — Ingestion now accepts .xlsx and .xlsm files up to 20,000 rows per sheet, with clearer upload validation errors.
    • Voice and performance — Inline performance cues for text-to-speech are now enabled, and the speech pipeline recovers more gracefully from transient failures.
    • Client stability — Six widget bugs fixed across idle timeouts, sentence splitting, and health monitoring, backed by 138 new tests.
    • Session continuation during outages — Kiosk deployments now continue a conversation after a connectivity interruption. The assistant acknowledges the gap and resumes without losing the session.
    • Test coverage — 336 new tests added across eleven chat modules.