Meet the team
Who writes this blog
8 people, all named: the engineers who deploy this software, the writers who document it, and the people who help customers choose it.
No ghost bylines, no "editorial team".
- Articles published
- 260
- Named authors
- 8
- Topics covered
- 17
Authors
Shalomi Umeshika
- Development
- Collaboration
- IAM & Security
Kelum Sampath
- Development
- Collaboration
- Regulation
Binuka Ranatunga
- Development
- Collaboration
- Jitsi Meet
Hiruna Kumara
- Development
- IAM & Security
- Collaboration
Dinesh Chathuranga
- Development
- AI Image Tools
- LLMs & APIs
Maneesha Shehara
- Development
- Collaboration
- LLMs & APIs
Avindi Nisansala
- Collaboration
- IAM & Security
- LLMs & APIs
Buddhika Jayawardhana
- Development
Frequently asked questions
Who writes the guides on the Meetrix blog?
Named members of the Meetrix team - DevOps engineers, technical writers and the people who talk to customers every day. Every article carries a byline that links to the author profile you can see on this page. We do not publish under generic names such as "admin" or "editorial team".
Are the deployment steps actually tested?
Yes. Developer guides are written while deploying the product on a live AWS or GCP stack, and the screenshots come from that run. When a vendor changes an installer or a console screen, we re-run the deployment before updating the article.
Do engineers review the comparison articles?
Technical claims in comparisons and alternatives articles are checked against our own deployments of those products, and reviewed by the engineer who maintains the corresponding image before publishing.
Do you use AI to write these articles?
AI tools help with research, drafting and editing. Every article is planned, checked and signed off by the named human author whose byline it carries, and for developer guides the commands, configuration and screenshots come from a real deployment rather than from a model.
How often are articles updated?
Guides are revisited when the underlying product ships a breaking change, when a cloud console changes, or when a reader reports something that no longer works. The publish date shown on each article reflects its most recent substantive update.
How do I report an error in an article?
Email the team at support@meetrix.io with the article URL and what you hit. Corrections that change the outcome of a guide are applied to the article itself rather than buried in a comment.