Why StayFn exists

Hi, I'm Costin.

I have spent my career writing the interfaces that connect business systems to Oracle OPERA, mostly in hospitality and casino gaming. As an Oracle/MICROS Custom Solutions architect I built custom OXI and OWS integrations for MGM Resorts, Wynn, Las Vegas Sands, Hyatt and Fairmont, and I wrote the first casino player-tracking interface to OPERA PMS, still in production across the Las Vegas Strip and Macau. Since 2019 I have been the lead engineer on two hospitality software platforms, and today I move legacy OXI and OWS interfaces to OHIP REST APIs and event streaming as properties move to OPERA Cloud.

Every one of those integrations started the same way. Before writing the few dozen lines the business asked for, someone spent weeks on authentication, rate limits, retries, hotel configuration and monitoring. Then the next project did it all again, a little differently, and someone had to keep all of them running.

I built StayFn so that work is done once, and done properly. Developers write only the business logic, as small C# functions. Everything around it, from tokens and rate limits to retries, events, audit and tenant isolation, is the platform's job, the same for every integration and every hotel.

I also run AI engineering in production: an agentic delivery pipeline on Claude Code, with MCP tool servers that give the assistant facts instead of guesses. StayFn's MCP server comes from that experience. An AI assistant writes good OPERA Cloud integrations when it can look up the real API, so StayFn gives it exactly that.

If you are moving integrations to OPERA Cloud, or building new ones, I would be glad to talk. I work in English, French and Romanian.

hello@stayfn.com · LinkedIn