Hi, I'm Amey Lokare

Problem

VoIP operators often split day-to-day work across a PBX, a billing tool, and separate support processes. That makes provisioning slow, billing easy to get wrong, and customer self-service hard to offer.

Solution

Built a role-based operations panel that lets staff and resellers manage telephony configuration, usage, billing, and support in one product, with a customer-facing portal and a browser softphone.

Key Features

• • Multi-tenant account structure with super-admin, admin, reseller, and client roles
• • Provisioning for extensions, DIDs, carriers, trunks, routes, queues, and ring groups
• • Call detail records, call recordings access, and operational dashboards

Problem

Teams that need per-machine internet egress usually end up editing proxy and firewall configs by hand. That is slow, easy to break, and hard to audit when several machines need different upstream routes.

Solution

Built a self-hosted gateway product: operators add proxies, onboard machines or VPN peers, assign a route, and the appliance applies the networking change through generated configuration rather than manual server edits.

Key Features

• • Proxy inventory with create, import, connectivity tests, and health checks
• • Virtual-machine discovery and onboarding, including per-machine route assignment
• • WireGuard peer management with config/QR onboarding

Problem

Learners of regional Indian languages often face apps that are either too generic or too heavy. They need a simple phone-friendly way to study everyday phrases, with native script and clear meaning, even when connectivity is limited.

Solution

Built a lightweight learning app that keeps lessons as local content. Users pick a language, open a category, and study phrase cards. Content can be prepared in a spreadsheet and converted to JSON, so the product can grow without building a CMS first.

Key Features

• • Language selection for Kumaoni and Garhwali
• • Category-based lessons such as greetings, family, food, travel, and polite expressions
• • Phrase cards with native script, transliteration, and English meaning

Problem

Support organizations need a controlled way to manage technicians, customers, remote-support access, sessions and concurrent usage without exposing the underlying infrastructure directly to customers.

Solution

EZYACCESS is a product/control layer around remote-support infrastructure. It owns tenants, users, RBAC, support codes, guest access, devices, session lifecycle, concurrent slot limits, and administrative controls. MeshCentral remains the remote-desktop transport in production rather than a customer-facing system.

Key Features

• • Multi-tenant organizations with server-side role visibility (Owner, Admin, Agent)
• • Technician support codes: hashed 6-digit codes bound to an organization
• • Guest/customer portal so the customer can verify a code without creating an account