A product should own the work and the rules around it. Every way into it—an operator's chat, an application's API call, an agent's tool call—should make it more useful without becoming a way around those rules.
Products
What ApexAi builds
Scrawl collects web content and keeps it as owned artifacts and versioned datasets. Communications runs customer support and business messaging over SMS, WhatsApp, and Telegram Business, plus transactional email, on the customer's own provider accounts, with or without the AI the customer chooses. DevOps corrects failures in the systems a customer connects, only with actions the customer allows, and proves each fix by observation; its engine is in development and its managed service is planned.
Problems
Why these three
Each starts from work that is easy to begin and hard to run well: data you need to trust later, customers you may only contact with permission, and systems that must be repaired without giving automation free rein. The products are built around keeping that work correct over time.
Callers
Operators, software, agents
People operate the products directly, applications integrate through ApexAPI, and AI agents act through ApexMCP. All three reach the same product core, so adding a caller never adds a way around its rules.
Standard
Claims you can check
Each product is built from the operating problem outward, and every public claim is labelled by its real state: built, in development, or planned. Nothing is called available until a customer can use it.