Built inside Ruh AI and used on its own marketing first. Now a managed service: a system for repeat work, a team for decisions.
Where Ciny started
Every feature exists because Ruh AI's own marketing needed it.
Read the Ruh AI case studyWe set out to fix our own marketing. CinySuite, the platform behind Ciny, started inside Ruh AI, a construction-AI company. Its designer-led team kept losing the content war to the calendar. So we built the machine we wished existed, ran our own company on it, and only then productised it.
Every feature exists because Ruh AI's own marketing needed it: the review room because we would not publish unreviewed AI content under our brand, the persona panel because “looks fine to me” is not quality control, the cadence engine to coordinate approved publishing without relying on a manual calendar.
We believe the production layer of content should be automated and the judgment layer should not. That split is baked into the architecture: the engine can research, write, design and schedule alone, but going live is a human's single click, and Auto Publish stays off by default.
The delivery model
Ciny is a managed service supported by an AI platform. You work with the team, not the tools.
See how delivery worksThe crew
Named software agents, not human employees. Each has a defined workflow. Availability and human review differ by module.
Compare module availabilityLead Marketing Agent · Software agent
Turns research into content briefs for the rest of the crew. Search Console evidence feeds her briefs where the SEO module is connected.
Blog Writer · Software agent
Writes long-form articles with covers, inline infographics and internal links, checks each one against an SEO score gate and publishes to a Strapi CMS after review.
Social Media Manager · Software agent
Builds branded statics and carousels from your brand pack, writes per-platform captions and publishes to LinkedIn, Instagram and Facebook.
Data Hub Keeper · Software agent
Keeps the Data Hub, seven ground-truth files written with your team that your content is checked against. Its proof file is the only source of figures content may state, and automated claim checks flag other figures for review.
Analytics Lead · Software agent
Runs the AI reader panel, 20 personas by default, that scores content after it is written, and archives the feedback. Scores can guide revision, but they do not block publishing or prove customer response.
Newsletter and Email · Software agent
Drafts newsletter issues from your blogs and trending sources for review. Scheduled and drip email are planned.
The house rules
The rules behind every claim, release and connected account.
Read the editorial standardSources distinguish first-party Ruh AI measurements, publisher-reported customer outcomes, historical search demand and workflow scope. Results are not forecasts. Availability is labelled Live, Available, In build or Planned.
Publishing is review-first by default, and Ruh AI's own publishing runs with Auto Publish off. A client's configuration cannot switch Auto Publish on.
Credentials sit in a per-client vault. The Ciny team sees masked key names, never values, and each client's dashboard has its own installation and data store.
Work in practice
Two stories with different evidence levels. Read each source and its limits.
All case studiesOrganic leads, with the evidence attached.
Weekly organic leads rose from 6 in early July to 20 in the week of 24 August 2026. August paid spend was $0.
A more connected marketing workflow.
Ruh AI reports 37% more leads for Rapid Innovation after introducing AI-supported research, publishing and lead qualification.
Tell us what you sell, who you need to reach and where the work gets stuck. We agree the scope before any work starts.
