Integrations & Automations
Engineering The Future.
Explore the technical innovations and integrations powering my applications, featuring secure authentication, highly scalable databases, and modern architectures.
01Authentication & Identity
I’ve used Clerk in products where I needed a polished authentication experience without compromising on security or control.
What I worked on
- Set up email and social sign-in with secure session handling
- Protected routes and APIs using middleware-based authentication
- Implemented role-based access for different user types
- Connected user identity cleanly across frontend and backend services
- Managed onboarding, profiles, and session persistence with minimal friction
I used BetterAuth when I needed more control over how authentication and authorization worked behind the scenes.
What I worked on
- Built JWT-based authentication flows with refresh token handling
- Designed custom auth logic for internal tools and admin dashboards
- Integrated authentication directly with Neon Postgres and Drizzle ORM
- Applied permission-based access across B2B and B2C applications
- Ensured secure session handling aligned with modern best practices
For GetAVisa, the backend is powered by Convex, so using Convex Auth was a natural choice. It allowed me to keep authentication tightly coupled with backend logic while maintaining strong security for both B2B and B2C flows.
Why I chose it & what I implemented
- Used Convex Auth for seamless integration with the existing Convex backend
- Secured real-time queries and mutations using authenticated user context
- Enforced data access rules directly at the backend level
- Supported both B2B and B2C user models with consistent authorization
- Reduced complexity by handling auth and data security in one place
How I Approach Authentication
- Choose auth tools based on architecture, not trends
- Enforce authorization at both UI and backend layers
- Keep security simple, explicit, and auditable
- Design auth systems that scale with product growth
- Avoid over-engineering while ensuring strong access control
02Payments & Billing
I’ve integrated Razorpay for applications targeting the Indian market, ensuring smooth and reliable payment experiences across different user scenarios.
What I worked on
- Implemented secure checkout flows with server-side payment verification
- Integrated webhook handling to track payment status and avoid inconsistencies
- Built failure-safe logic for retries and partial payment scenarios
- Connected payment events with internal order and billing systems
- Ensured compliance with local payment requirements and best practices
I’ve integrated Stripe for products requiring international payments and advanced billing capabilities, with a strong emphasis on security and operational clarity.
What I worked on
- Implemented 3D Secure card authentication to meet global compliance standards
- Set up auto-debit and recurring payment flows for subscriptions and renewals
- Built manual payout workflows for controlled fund disbursement
- Verified payments using secure webhooks and server-side validation
- Designed billing logic that supports both one-time and recurring charges
I integrated PayPal Wallet to support trusted, frictionless payments for international users, especially where card usage is lower or users prefer wallet-based checkout.
What I worked on
- Implemented PayPal Wallet Checkout for fast, one-click payments
- Built secure order creation, approval, and capture flows
- Verified payment status server-side to ensure transaction authenticity
- Handled success, cancellation, and failure states gracefully
- Enabled multi-currency payments for cross-border transactions
How I Approach Payments
- Always verify payments server-side, never trust the client
- Design webhook-first systems to handle async payment states
- Make payment flows idempotent and retry-safe
- Handle failures and edge cases as first-class scenarios
- Prioritize compliance, security, and user trust over shortcuts
03CRM & Business Systems
I integrated Zoho CRM for WorldVisa to capture, manage, and track leads directly from websites and applications.
What I worked on
- Connected website forms and funnels directly to Zoho CRM
- Automated lead creation and status updates
- Synced customer data between frontend systems and CRM
- Reduced manual data entry for sales and operations teams
- Ensured reliable data flow using secure API integrations
I integrated Zoho Books to handle invoicing and basic accounting workflows linked to user actions on the platform.
What I worked on
- Automated invoice creation based on user payments or actions
- Synced customer and transaction data with accounting records
- Handled tax, payment status, and invoice lifecycle updates
- Reduced accounting overhead through system-driven workflows
- Ensured financial data consistency across platforms
I integrated Zoho Payments to collect and track payments directly within Zoho’s ecosystem.
What I worked on
- Enabled online payment collection linked to CRM and Books
- Synced payment status automatically across systems
- Handled success, failure, and reconciliation flows
- Reduced payment tracking errors through automation
- Provided clear visibility into payment and customer status
I used Zoho Forms to collect structured data from users and push it seamlessly into backend systems.
What I worked on
- Embedded Zoho Forms into websites and landing pages
- Automatically pushed form submissions into Zoho CRM
- Used forms for lead capture, document requests, and inquiries
- Validated and structured incoming data for downstream workflows
- Improved lead response time through instant data availability
How I Approach CRM Integrations
- Treat CRM as a source of truth, not just a data sink
- Automate wherever possible to reduce manual operations
- Keep customer, payment, and accounting data in sync
- Design integrations that scale with business growth
- Prioritize clarity for sales, finance, and operations teams
04Analytics & Monitoring
I’ve used PostHog to move beyond basic metrics and truly understand how users interact with key features, helping guide both product and UX decisions.
What I worked on
- Implemented event-based tracking for critical user actions and core product flows
- Built separate dashboards for key features to clearly understand usage patterns
- Tracked onboarding funnels and feature adoption across the product
- Used behavioral data to identify drop-offs, friction points, and usability gaps
- Categorized users using UTM source tracking to understand where users come from
- Connected analytics insights directly to product improvements and UX changes
- Ensured privacy-aware tracking aligned with user expectations and regulations
I integrated Sentry to get real-time visibility into production issues and application performance.
What I worked on
- Set up real-time error monitoring for frontend and backend
- Tracked performance issues and slow transactions in production
- Used stack traces and context to debug issues faster
- Reduced production downtime by catching issues early
- Monitored releases to understand the impact of new deployments
I’ve used Microsoft Clarity to understand how users interact with the UI at a practical, human level.
What I worked on
- Integrated session recordings to observe real user behavior
- Used heatmaps to identify engagement and ignored UI elements
- Analyzed scroll depth and click patterns to improve layouts
- Identified usability issues that weren’t visible through metrics alone
- Used insights to refine UX and reduce user confusion
How I Use Analytics & Monitoring Together
- Use PostHog to understand what users are doing
- Use Clarity to understand how they’re doing it
- Use Sentry to understand where and why things break
- Combine data and observation to drive meaningful improvements
05Security & Rate Limiting
I used Arcjet to add an intelligent security layer that adapts to traffic behavior rather than relying on static limits.
What I implemented
- Applied context-aware rate limits based on endpoint sensitivity (auth, payments, forms)
- Enabled bot detection and automated challenge handling for suspicious traffic
- Protected high-risk workflows like login, OTP, and eligibility checks
- Reduced backend load by blocking abusive traffic before execution
- Tuned protection rules iteratively using real production traffic patterns
I used Upstash Redis to build precise, low-latency rate limiting suitable for serverless and distributed environments.
What I implemented
- Built sliding-window rate limiting instead of fixed limits to handle burst traffic
- Implemented user-, IP-, and token-based throttling for different access levels
- Applied stricter limits on anonymous traffic and relaxed limits for authenticated users
- Designed idempotent request guards for retry-heavy endpoints
- Ensured rate limiting logic worked consistently across multiple regions
Security Engineering Practices I Follow
- Secure the most expensive operations first
- Treat authentication, payments, and automation endpoints as high-risk
- Design controls that scale horizontally with traffic
- Avoid global limits that punish legitimate users
- Continuously refine rules based on observed abuse patterns
