حول Ryware - هندسة بحدود واضحة

Our team

Ryware is a team of 21, working together since 2020. The mix is deliberately broad enough to take a product from design through to production and then keep it running — backend, frontend and mobile engineering, architecture, database administration and data engineering, QA and UX under one roof.

Backend engineers

4

• C#
• .NET
• Python
• Go
• Apache Spark
• RabbitMQ

Frontend engineers

4

• React
• Angular
• Svelte
• SolidJS

Mobile developers

4

• React Native
• Ionic
• Apache Cordova
• PhoneGap

DBAs & data engineers

3

• Microsoft SQL Server
• PostgreSQL
• MongoDB
• Snowflake

Architects

2

• Google Cloud Platform
• Docker
• Kubernetes

QA engineers

2

UX designers

2

We pick the stack per project rather than defaulting to one. On the front end that means React and Angular on most client work, with Svelte and SolidJS where a lighter runtime is worth having — this site is built in SvelteKit. On the back end it is mostly C#/.NET and Python, with Go where a small, fast binary beats a service, and Apache Spark once data volumes justify distributed processing.

On mobile we work in React Native and Ionic, and we still maintain Apache Cordova and PhoneGap codebases. That last part is deliberate: plenty of working hybrid apps were built on Cordova or PhoneGap and are now hard to find anyone willing to touch. We will keep them running, or plan the migration off them, rather than insisting on a rewrite as the opening move.

Our three database administrators also work as data engineers — the same people build and operate the ETL platforms behind our data work, which is why database and pipeline decisions get made by engineers who will be running the result.

We do not publish individual profiles. If you want to know who would actually work on your project, ask during scoping — you will meet them before you commit to anything.

Platforms and integrations

Third-party services we have integrated in production. The payment list is deliberately specific: Stripe and RevenueCat cover global card and mobile-subscription billing, while Tranzila and CardCom are the Israeli gateways most local projects actually need — and the ones hardest to find a team that has already shipped against them.

Cloud & orchestration

• Google Cloud Platform
• Docker
• Kubernetes

Messaging & caching

• RabbitMQ
• Apache Kafka
• Redis

Payments

• Stripe
• RevenueCat
• Tranzila
• CardCom

Platform services

• Google Maps Platform
• Firebase Cloud Messaging