# MFactor: full content in English > The full text of MFactor's public pages in English, generated at build time > from the same source as the site. For the short summary, see /llms.txt. Site: https://www.mfactor.dev/en Generated on: 2026-10-19 --- # Your tech ally for now and what's next > Top-quality technology that turns challenges into a competitive edge, from the first commit to production infrastructure. URL: https://www.mfactor.dev/en Site: MFactor (https://www.mfactor.dev) ## What we do - [MLabs: Software development](https://www.mfactor.dev/en/services/mlabs): Custom systems and licensed software, web and mobile apps, APIs and integrations. - [MReach: E-commerce and online presence](https://www.mfactor.dev/en/services/mreach): Your own online stores, social commerce and business websites built to convert. - [MHost: Cloud infrastructure](https://www.mfactor.dev/en/services/mhost): Managed cloud, Kubernetes, databases and observability. - [M-AI & ML: Artificial intelligence](https://www.mfactor.dev/en/services/mai): LLMs, AI agents, automation and predictive analytics built into the systems you already have. - [MRecovery: Fixing software built with AI](https://www.mfactor.dev/en/mrecovery): We find and fix what's wrong with AI-built websites, apps and systems that throw errors, crash when more people use them or that nobody can maintain. - [MPartner: White label for agencies](https://www.mfactor.dev/en/services/mpartner): Behind-the-scenes development that agencies, studios and freelancers resell under their own brand. - [MServices: Managed IT in Leme, Brazil](https://www.mfactor.dev/en/mservices): Remote support, automations and care for your equipment for a flat monthly fee, only for companies in Leme. ## By the numbers - **75,000+ nodes**: of infrastructure managed in production. - **35,000+ people**: reached by the platforms we've delivered. - **15+ industries**: served, from healthcare and retail to agribusiness and manufacturing. - **In-house team**: dedicated support, with no outsourced development. ## Where we are MFactor is based in Leme, in the São Paulo countryside. We work with companies across the region, in cities like Pirassununga, Araras, Rio Claro, Limeira, Piracicaba and Campinas, and all over Brazil. - [Technology in Leme and the São Paulo countryside](https://www.mfactor.dev/en/leme-sp): the cities in the region and what we do for companies in the countryside. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # Custom software development > Scalable systems made to fit, from MVP all the way to production. Audited code, written by our own team. URL: https://www.mfactor.dev/en/services/mlabs Site: MFactor (https://www.mfactor.dev) Custom-built and licensed systems: web and mobile applications, APIs and integrations, for companies of any size. ## What we deliver - Web & Mobile - APIs & Integrations - Agile process - Ongoing support **Who it's for:** Startups, small and mid-sized businesses, and large enterprises ## Why MLabs - **Fully custom**: Every line of code is written for your business, not adapted from a template. - **Scalability**: Architecture that grows with your operation, so you never have to rewrite it. - **Security from day one**: Audited code and security practices applied throughout development. ## Who it's for - **Startups**: that need to validate an MVP and scale fast. - **Small and mid-sized businesses**: looking to automate processes and run more efficiently. - **Large enterprises**: that need solid, integrated systems. - **Entrepreneurs**: with a new idea that needs modern technology to get off the ground. ## Frequently asked questions ### How much does custom software cost? It depends on the scope: the number of screens, the integrations you need, how many users you'll have and the timeline. We run a technical assessment before quoting, so the number reflects your actual project and not a market average. The assessment is free. ### How long does it take to build a system? A working MVP usually takes 6 to 12 weeks; enterprise systems with lots of integrations take longer. We work agile and ship in iterations, so you see the product running well before the project ends. ### Do I own the source code? Yes. On custom development projects the code is yours, delivered in your own repository. We also offer licensed systems, for when it makes more sense to start from a ready-made base and cut cost and time. ### Do you provide support after launch? Yes. We keep supporting the system after launch, with fixes, improvements and monitoring. It's the same team that built it, not an outsourced help desk that has to learn the project from scratch. ### Can you integrate with the systems I already use? Yes. We integrate with ERPs, CRMs, payment gateways, electronic invoicing (nota fiscal) systems and third-party APIs. When there's no API, we look at alternatives such as file imports or automating the existing workflow. ### Do you build software for companies in Leme and the São Paulo countryside? Yes. MFactor is based in Leme and builds custom systems for companies in Leme, Pirassununga, Araras, Rio Claro, Limeira and the rest of the São Paulo countryside, plus clients all over Brazil. The technical assessment is free and you follow the project stage by stage, with the same team from kickoff to support. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # E-commerce and online presence > Your own online store, social commerce and business websites, all built to sell. Checkout, SEO and analytics from day one. URL: https://www.mfactor.dev/en/services/mreach Site: MFactor (https://www.mfactor.dev) Full e-commerce stores, shops connected to social media and strategic business websites, with checkout, integrations and technical SEO. ## What we deliver - Stores & checkout - Social commerce - Technical SEO - Analytics **Who it's for:** Retailers, brands, B2B companies and content creators ## Why MReach - **Direct sales**: A store of your own cuts marketplace fees and puts the margin back into your business. - **Everything connected**: Payments, shipping, ERP and social media talking to each other in a single flow. - **Easy to find on Google**: Technical SEO and fast pages that bring in organic traffic, so you don't depend on paid ads alone. ## Who it's for - **Retailers**: who want to sell direct, without relying on marketplaces alone. - **Brands**: that need a channel of their own and a direct relationship with their customers. - **B2B companies**: with a catalog, price lists and recurring orders. - **Influencers and creators**: who sell to their own audience. ## Frequently asked questions ### How much does it cost to build an online store? It depends on the catalog, the integrations (ERP, shipping carrier, payment methods) and how much the checkout needs to be customized. A lean, well-built store costs far less than an operation with inventory spread across several distribution centers and complex tax rules. That's why we quote after we understand how you operate. ### Is it better to have my own store or sell on a marketplace? They complement each other. A marketplace brings traffic, but it takes a commission on every sale and the customer base stays with the marketplace. Your own store gives you back the margin and a direct relationship with the buyer. In practice, most of our clients keep both channels running and connected. ### Will the store show up on Google? We work on technical SEO from day one: semantic structure, product structured data, performance, clean URLs and a sitemap. That's the foundation for organic rankings. How fast you climb after that depends on content and on the competition in your category. ### Can it integrate with Instagram and WhatsApp? Yes. We set up a catalog connected to Instagram and Facebook and customer service through WhatsApp Business, so the buying process doesn't break when a customer comes in from social media. ### Can you migrate a store that already exists? Yes, including products, customers, order history and 301 redirects from the old URLs. That last step is what keeps the rankings you've already earned on Google. ### Do you build online stores for companies in the São Paulo countryside? Yes. For retailers in Leme and the São Paulo countryside, having your own store is how you sell beyond your city without depending only on marketplaces. MFactor builds the store with checkout, shipping, invoicing and integration with the ERP you already use, and works with companies in the region and all over Brazil. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # Managed cloud infrastructure > 24/7 performance, availability and security on AWS, Google Cloud, Azure or bare metal. Our team handles the day-to-day operations. URL: https://www.mfactor.dev/en/services/mhost Site: MFactor (https://www.mfactor.dev) Managed cloud infrastructure with Kubernetes, databases, observability and high availability on the major cloud platforms. ## What we deliver - Kubernetes - Managed databases - Observability - CI/CD **Who it's for:** SaaS companies, e-commerce businesses, apps and enterprise systems ## Why MHost - **High availability**: Redundancy and proactive monitoring to keep your operation up and running. - **Scale on demand**: The infrastructure keeps up with traffic spikes, without re-engineering every time you grow. - **Costs under control**: Architecture sized for your real usage, not permanently provisioned for the worst case. ## Who it's for - **SaaS companies**: with a product in production and steady growth. - **Online stores**: that can't go down on their busiest days. - **Mobile apps**: with their own backend and traffic that rises and falls. - **Enterprise systems**: that require availability and compliance. ## Frequently asked questions ### Which cloud providers do you work with? AWS, Google Cloud, Azure, Hetzner and Vercel, plus bare metal when the cost justifies it. We choose based on your workload and budget, and we don't favor any provider for commercial reasons. ### Do I really need Kubernetes? Not always. Kubernetes pays off when you have several services, variable scaling and frequent deploys. For a single, stable stack, a well-configured VPS with Docker does the job for a fraction of the operating cost. We tell you which case you're in before we propose anything. ### Can you migrate my existing infrastructure? Yes. We map your current environment, design the target architecture and migrate in stages, with a rollback plan. The goal is to switch over without any downtime your end users would notice. ### How does monitoring work? Metrics, logs and tracing with Prometheus and Grafana, with alerts set up for the symptoms that matter in your operation. The goal is for the team to know about a problem before a customer opens a ticket. ### Can you lower my cloud bill? Almost always. Most of the waste comes from oversized resources, forgotten environments left running and storage with no lifecycle policy. We do that review before proposing any change to the architecture. ### Does a company in the São Paulo countryside need its own server? Hardly ever. For companies in Leme and the São Paulo countryside, managed cloud usually costs less and is safer than keeping a server in the back room: backups, updates and monitoring are handled by the team that manages it. MFactor looks at your case in the free assessment and tells you when a simple VPS is enough. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # Artificial intelligence and machine learning > LLMs, agents and machine learning built into the systems you already use, instead of yet another generic tool to manage. URL: https://www.mfactor.dev/en/services/mai Site: MFactor (https://www.mfactor.dev) Integration of LLMs, AI agents, automations and predictive analytics into the systems and business processes a company already runs. ## What we deliver - LLMs - AI agents - Automation - Predictive analytics **Who it's for:** Companies that want to apply AI to their existing processes and systems ## Why M-AI & ML - **Built for you**: Designed around your context and your data, not an off-the-shelf product. - **Real integration**: Connected to the databases, CRMs, ERPs and APIs your company already has. - **From raw data to production**: Complete data pipelines that end with a model actually running in production. ## Frequently asked questions ### How can artificial intelligence help my business? The fastest wins are usually in repetitive, text-heavy tasks: support triage, reading documents, generating reports and classifying data. We start with the process that eats up the most hours today and measure the result before we expand. ### Do I need a lot of data to get started? For LLM-based work, no. It runs on the documents and databases your company already has. You only need a large volume of historical data for predictive models trained from scratch, which is a narrower case. ### Will the AI have access to my company's data? Only to what you explicitly allow, and we define that together. We use scoped access control, usage logs and, when the data is sensitive, options that keep the processing inside your own infrastructure. ### What's the difference between hiring you and using ChatGPT? A generic tool doesn't know your data and can't take actions in your systems. We build agents connected to your ERP, CRM and database that answer with information from your operation and trigger the next step in the process. ### Can you add AI to a system I already have? Yes, and that's the most common case. We connect to your production system through its API, without rewriting what already works. The AI layer runs as a separate service. ### Can small companies in the São Paulo countryside use AI? Yes, and they don't need to build a data team. For companies in Leme and the São Paulo countryside, the uses that usually pay off fastest are WhatsApp customer service that answers from the company's own documents, automatic reading of invoices and orders, and reports generated from the ERP. MFactor starts with the process that takes the most time today and measures the gain before going further. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # We fix websites, apps and systems built with AI that don't work > It got built fast and started breaking once real users showed up. We open the code, find what's wrong and get it working, and we review the database and infrastructure too. URL: https://www.mfactor.dev/en/mrecovery Site: MFactor (https://www.mfactor.dev) Diagnosis and repair of websites, apps and systems made with AI tools or vibe coding that throw errors, can't handle more users or that nobody can maintain, with a review of the database, infrastructure, tests and documentation. ## What we deliver - Code assessment - Database & Infra - Fixes in production - Tests & Documentation **Who it's for:** Companies and founders whose AI-built software fails in production ## Why MRecovery - **Assessment before the quote**: You get a report on what's broken, why it breaks and what it costs to fix. Only then do you decide. - **No starting from scratch**: We keep what works. Rewriting is a last resort, and when we do it, it's just one part. - **Code someone else can understand**: We hand over an organized repository, tests and documentation. The system no longer depends on whoever built it. ## What MRecovery is MRecovery is the MFactor service that rescues software built with artificial intelligence. Lovable, Bolt, v0, Cursor, a freelancer pasting code from ChatGPT: how it got made doesn't matter. What lands here is a system that was promised, that even worked in the demo, and that couldn't handle real use. AI writes code fast, and that's a good thing. The problem is that it writes what you asked for, not what the system needs. It doesn't know the orders table will hit 200,000 rows within a year, that tax ID numbers need validating, that passwords can't go into the database as plain text, or that the free hosting plan won't survive Black Friday. Engineers know that. When there's no engineer on the project, nobody makes those calls, and the bill comes due once people already depend on the system. The symptoms are familiar. It works with ten users and crashes with a hundred. A screen takes eight seconds to load because it queries the database once per row. One customer's data gets mixed up with another's. The site looks like a thousand others, because AI designs whatever is most common. And then there's the SaaS that brings in money, with customers paying every month, but can't grow because every new feature breaks two old ones. ## Signs your system needs recovery - **The bug comes back in a new place**: You ask the AI to fix it, it changes something else, and the problem shows up again on another screen. Without tests, every fix is a gamble. - **It goes down when people show up**: It ran fine in the demo. With fifty people using it at once, it freezes, slows to a crawl or takes the server down. - **Data goes missing or gets mixed up**: One customer sees another customer's order. A record disappears. There's no log to tell you when it happened or why. - **A site that looks like everyone else's**: The layout is what the tool hands out to everyone. Nobody recognizes your brand in it, and neither does Google. - **It makes money, but it can't grow**: Customers pay every month, but every change to the code is nerve-wracking. The team is afraid to touch it. - **Nobody knows what's in there**: Whoever built it is gone, or it was built by AI. There's no documentation, no tests and no organized repository anyone could take over. ## What the recovery includes - **Assessment**: we go through the code, the database and the infrastructure and tell you what's wrong, ranked by risk. - **Fixes**: bugs, slow queries and security holes, starting with whatever takes the system down. - **Database**: structure, indexes, migrations and backups. That's usually where AI-built systems are weakest. - **Infrastructure**: hosting, environment variables, logs, monitoring and cost. The system moves off the free plan it has outgrown. - **Tests and version control**: the minimum so the next change doesn't break the last one. - **Documentation**: what the system does and how to run it, so you don't depend on whoever built it or whoever fixed it. ## How it works - **1. Access and review**: You give us access to the code, the database and the hosting. We read through all of it before we weigh in, and we don't change anything at this stage. - **2. Assessment report**: What's broken, why it breaks and what happens if it stays that way, ordered by risk. Each item comes with the cost to fix it. - **3. Stabilization**: First, whatever takes the system down or leaks data. We back up the database before touching anything in production. - **4. Database and infrastructure**: Indexes, queries, migrations and backups. Hosting sized for real usage, with logs and monitoring. - **5. Tests and repository**: The code moves to an organized repository, with tests on the critical parts and a review for every change. - **6. Handover and next steps**: Documentation of what was done and how to run it. Then it's your call: keep going with your own team, or have MFactor handle operations. ## Who it's for If the system can't be saved, we'll tell you. Sometimes the right answer is to rebuild one part with MLabs and keep the rest. But that comes after the assessment, not before. - **Business owners**: who paid for a system and got something that doesn't do what was agreed. - **SaaS founders**: with a live product and paying customers, who can't ship anything new without breaking what's already there. - **Companies**: that built an internal tool with AI and now depend on it more than it can handle. - **Agencies and freelancers**: who delivered a project built with AI and need engineering to make good on it. ## Frequently asked questions ### My system was built with Lovable, Bolt or Cursor. Can you work on it? Yes. These tools generate ordinary code, usually React, Node and Supabase or Firebase. The difference is that it comes without the structure an engineering team would put in: no tests, no separate environments and a database that's wide open. We move the code into a repository and work on it like any other project. ### Do I need to rebuild everything from scratch? In most cases, no. The assessment separates what works from what needs to be redone, and rewriting is the last resort. When a part can't be saved, we rebuild just that part with MLabs and connect it to the rest. ### How much does it cost to recover a system? It depends on the state it's in, which is why we only set a price after the assessment. The assessment has a fixed scope, and the report is yours to keep even if you decide not to go ahead with the fixes. ### The system is live with customers. Do you need to take it down to fix it? No. We work in a staging environment separate from production, and changes go live in agreed windows, after a backup. The system keeps serving customers throughout the recovery. ### What if I don't have access to the code? That happens when someone else built the project. We walk you through how to request the repository and credentials, and what to do if they don't hand them over. With access to the database and hosting, we can already start the assessment. ### Once it's recovered, who looks after the system? Your call. We hand over the repository, the documentation and the environment for your team to take over, or MFactor keeps looking after it through MHost, with monitoring and support. ### Do you work with companies in Leme and the São Paulo countryside? Yes. MFactor is based in Leme and works with companies in Pirassununga, Araras, Rio Claro, Limeira, Piracicaba, Campinas and all over Brazil. The work is remote, with access to the code and the hosting, and meetings can be in person when the company is in the region. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # White label for agencies > Your agency sells, presents and signs. We build behind the scenes, on the agreed deadline, and our name never appears anywhere. URL: https://www.mfactor.dev/en/services/mpartner Site: MFactor (https://www.mfactor.dev) A white label development team for agencies, studios and marketing professionals: custom websites and systems delivered unbranded, with agreed deadlines, stage-by-stage follow-up and contractual confidentiality. ## What we deliver - No MFactor branding - Fixed deadline - Standard NDA - White label support **Who it's for:** Marketing agencies, design studios, freelancers and consultancies ## How it works - **Fast delivery**: Landing pages in 5 to 7 business days, company websites in 10 to 15. The date is agreed before we start. - **Confidence at every stage**: A staging environment live from week one and a direct technical contact. No ticket queue. - **Confidential by contract**: Standard NDA, no trace of us in the code or the footer, and no contact with the end client without your permission. ## Who it's for - **Marketing agencies**: that sell websites and systems but don't have an in-house tech team. - **Design studios**: that hand off the layout and need someone to build it. - **Freelancers and consultancies**: who want to take on projects bigger than they can handle alone. - **Growing agencies**: that need extra capacity without adding to payroll. ## Frequently asked questions ### What is white label development? Your agency sells the website under its own brand and we build it behind the scenes. The contract, the presentation and the relationship with the end client stay with the agency; we deliver the project without our name, brand or link anywhere in the code or the footer. ### Do you sign a confidentiality agreement? Yes, and it's standard on white label projects. We don't show the project in our portfolio, we don't appear in the footer and we don't contact the end client unless the agency authorizes it. If we need to join a meeting, we join as part of the agency's team. ### What's the turnaround time? A landing page takes 5 to 7 business days; a company website, 10 to 15; an online store or custom system depends on the scope and is agreed in the quote. The deadline is set before we start and every stage has a date, so the agency knows what to show the client and when. ### How does resale pricing work? You get a cost sheet by project type and set whatever margin you want for the end client. We don't interfere with your selling price or ask for exclusivity. Agencies with steady volume get different terms than one-off projects. ### Does the agency provide the layout, or do you design it? Both work. If the agency already has the layout in Figma, we build it exactly as designed. If not, we handle the design too, always within the visual identity the agency sets for the client. ### Who handles maintenance after delivery? It's up to you. We hand over the repository and the documentation for the agency to take over, or we keep providing technical support under white label, responding within the agreed time so the agency can serve the end client without depending on other vendors. ### Do you work with agencies in Leme and the São Paulo countryside? Yes. Agencies, studios and freelancers in Leme, Pirassununga, Araras, Rio Claro, Limeira and the rest of the São Paulo countryside can resell websites and systems built by MFactor under their own brand, with a standard NDA and no contact with the end client without authorization. The model works the same for agencies in any city in Brazil. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # MServices: Managed IT in Leme, Brazil > Your company's IT taken care of, without a technician on staff. Only available to companies headquartered in Leme, SP, Brazil. URL: https://www.mfactor.dev/en/mservices Site: MFactor (https://www.mfactor.dev) ## What we deliver - Fast remote support for most issues - Automations that take repetitive tasks off your plate - Support for the systems your company already uses ## Plans - **Essential: R$ 1,250/month**: Remote support for your company's systems (ERP, email, Office, e-invoicing software); DNS record setup (domain, email and website); Up to 3 automations a month; Up to 8 hours of support a month; Response within 1 business day. - **Professional: R$ 2,490/month**: Everything in Essential; Maintenance for up to 10 devices; 1 on-site visit a month; Up to 6 automations a month; Monthly report with your company's data; Up to 16 hours of support a month; Response within 4 business hours. - **Business: R$ 3,790/month**: Everything in Professional; Maintenance for up to 20 devices; 2 on-site visits a month; Up to 10 automations a month; Dashboard with your company's key metrics; Up to 28 hours of support a month; Response within 2 business hours. - **Full Management: R$ 5,290/month**: Everything in Business; Maintenance for up to 35 devices; Maintenance for your company's servers; 4 on-site visits a month; No limit on the number of automations; Monthly check-in meeting; Up to 45 hours of support a month; Response within 1 business hour. ## Terms Only available to companies headquartered in Leme, SP, Brazil. Parts, equipment and software licenses are billed separately. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # Project portfolio and case studies > Projects MFactor has delivered in healthcare, retail, agribusiness, manufacturing and education: platforms, online stores and infrastructure running in production. URL: https://www.mfactor.dev/en/showcase Site: MFactor (https://www.mfactor.dev) ## Public case studies - **EezyCare and EezyFamily**: Healthcare: more than 12,000 people served, with the operational workflow automated. - **Chepa**: Food retail. - **Livin**: Marketplace. - **Renovar Implementos**: Manufacturing. - **Emex Structures**: Manufacturing. - **BFX**: Services. - **Synapsia**: Technology. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # MFactor for developers and agents > All public content on this site is also served as Markdown, with no authentication and no HTML scraping. MFactor is a technology company in Leme, São Paulo, Brazil, and its API is described in OpenAPI. This page shows how to request both. URL: https://www.mfactor.dev/en/developers Site: MFactor (https://www.mfactor.dev) ## What we deliver - OpenAPI 3.1 spec - Accept: text/markdown - .md files for every route - llms.txt - Official CLI ## Quick start Request any page on the site with the Accept: text/markdown header and the response comes back in Markdown, at the same URL a browser uses to get HTML. That's the convention described at acceptmarkdown.com, built on the content negotiation mechanism in RFC 9110. ```bash # The home page in Markdown, at the canonical URL curl -sH 'Accept: text/markdown' https://www.mfactor.dev/ # A service page, showing only the response headers curl -sIH 'Accept: text/markdown' https://www.mfactor.dev/servicos/mlabs # No header at all: the same content at the explicit .md URL curl -s https://www.mfactor.dev/servicos/mlabs.md ``` ## The response contract - **Content-Type**: text/markdown; charset=utf-8 when Markdown wins the negotiation; text/html; charset=utf-8 otherwise. - **Vary: Accept, Accept-Encoding**: Present on every negotiated response, so an intermediary cache doesn't hand HTML to a client that asked for Markdown. - **Link: rel=alternate**: Points to the equivalent .md file, per RFC 8288, for clients that discover representations through links instead of headers. - **406 Not Acceptable**: The response to an Accept header that only allows formats we don't serve. The body lists the available representations in plain text. - **404 Not Found**: The response for a path that doesn't exist, with a short body pointing to the sitemap and the llms.txt. Never a 200 with the app shell. ## Machine-readable files - [/llms.txt](https://www.mfactor.dev/llms.txt): a summary of the company, its services and its use cases, in a single file. - [/llms-full.txt](https://www.mfactor.dev/llms-full.txt): the full text of every page and blog post, in Markdown. - [/en/llms-full.txt](https://www.mfactor.dev/en/llms-full.txt): the same full text with the pages in English. The blog is only in the Portuguese file. - [/es/llms-full.txt](https://www.mfactor.dev/es/llms-full.txt): the same, with the pages in Spanish. - [/agent-instructions.md](https://www.mfactor.dev/agent-instructions.md): when an agent should recommend MFactor and how to reach it. - [/sitemap.xml](https://www.mfactor.dev/sitemap.xml): the list of public URLs, regenerated on every build. - [/openapi.json](https://www.mfactor.dev/openapi.json): the OpenAPI 3.1 spec for API v1, with an operationId and JSON schemas for every operation. - [/.well-known/api-catalog](https://www.mfactor.dev/.well-known/api-catalog): the RFC 9727 API catalog, which points to the spec and to this documentation. - [/robots.txt](https://www.mfactor.dev/robots.txt): what's open to crawlers and AI bots, agent by agent. - **JSON-LD**: every page carries a schema.org @graph with Organization, WebPage, BreadcrumbList and, on service pages, Service and FAQPage. ## MFactor API and OpenAPI MFactor's public REST API lives at /api/v1 and is described in OpenAPI 3.1 at /openapi.json. Every operation has an operationId, a description and typed JSON schemas for input and output, so you can turn the file into a function-calling tool without editing it. The catalog at /.well-known/api-catalog (RFC 9727) points to the same spec. No key needed. GET /api/v1 returns the version index, with MFactor's location in Leme, SP, and the area it serves in the São Paulo countryside; GET /api/v1/servicos and GET /api/v1/servicos/{slug} return the service lines with their audience, sections and frequently asked questions; GET /api/v1/paginas lists the public pages with their Markdown URL. Both catalogs answer in English with ?lang=en (or in Spanish with ?lang=es), and their links point to the pages in that language. POST /api/v1/contato sends a message to the sales team, the same path the site's form uses at /api/contato. ```bash # The version index: status, limits and endpoints curl -s https://www.mfactor.dev/api/v1 # One service line as JSON curl -s https://www.mfactor.dev/api/v1/servicos/mlabs # A contact request. This sends a real email to the sales team: # use the real details of the person who wants to talk to MFactor. curl -s https://www.mfactor.dev/api/v1/contato \ -H 'Content-Type: application/json' \ -d '{"nome":"Jane Smith","email":"jane@example.com","mensagem":"We need to connect our store to the ERP by March.","idioma":"en"}' ``` ## Versions and deprecation The API version is part of the path: /api/v1. Within a version, only backward-compatible changes go in (new fields in responses, new endpoints, new optional parameters), and clients should ignore fields they don't recognize. Removing or renaming a field, changing a type or making a parameter required means a new version, /api/v2, and the previous one keeps responding. When a version is deprecated, every response from it starts carrying the Deprecation header (RFC 9745) with the date of the decision, the Sunset header (RFC 8594) with the date after which it may stop responding, and a Link rel="deprecation" pointing to the migration guide. The two dates are at least six months apart. The GET /api/v1 index carries the same dates in the deprecation and sunset fields; right now both are null, because v1 is the current version. ## API rate limits Every API response carries the RateLimit-Policy and RateLimit headers, in the format of the IETF draft draft-ietf-httpapi-ratelimit-headers. The first gives the quota and the window; the second, how much is left and how many seconds until the window resets. Go over the limit and you get a 429 with Retry-After in seconds. The counter lives in the memory of each function instance. It's a safety cap against runaway loops, not a contractual quota: respect the headers and you'll never see a 429. - **leitura (reads)**: 60 requests per minute on the API's GET endpoints. Header: RateLimit-Policy: "leitura";q=60;w=60. - **contato (contact)**: 10 submissions every 10 minutes on POST /api/v1/contato, because each one turns into an email a person reads. Header: RateLimit-Policy: "contato";q=10;w=600. ## API errors Every API error comes back as JSON, in the RFC 9457 Problem Details format, with Content-Type: application/problem+json. Besides type, title, status and detail, the body carries code, a stable identifier you can branch on; field, the field that caused the error; and hint, what to change so the next attempt works. A path that doesn't exist under /api returns a 404 in the same format. - **invalid_json**: the body isn't a JSON object. Send Content-Type: application/json. - **name_required, name_too_short, name_too_long**: the nome (name) field, 2 to 120 characters. - **email_required, email_invalid**: the email field, a valid address of up to 160 characters. - **phone_invalid**: the phone number has to be a Brazilian number with the area code; with "idioma": "en" or "es" in the body, an international number with the country code works too. It's optional, so you can leave it out. - **message_required, message_too_short, message_too_long**: the mensagem (message) field, 10 to 5,000 characters. - **method_not_allowed**: the endpoint doesn't accept that method. The response carries the Allow header. - **rate_limited**: rate limit exceeded. Wait the number of seconds in Retry-After before trying again. - **service_not_found**: that service slug doesn't exist. The hint lists the valid ones. - **lang_invalid**: the lang parameter isn't one we know. Use pt, en or es; without it, the response is in Portuguese. - **email_delivery_failed, email_not_configured**: a server failure, not a problem with the request. Try again in a few minutes or use WhatsApp. - **not_found**: the path doesn't exist. Comes back as JSON under /api and for clients that send Accept: application/json. ## Official CLI The @mfactor/cli package wraps the calls above in short commands, for when you'd rather script a few reads than write an HTTP client. It keeps no state and needs no key: same public content, same public URLs. ```bash npx @mfactor/cli servicos # the service lines, as text npx @mfactor/cli docs mlabs # one page in Markdown npx @mfactor/cli llms --full # the full content of the site npx @mfactor/cli sitemap # the public URLs, one per line npx @mfactor/cli contato --json # the contact channels, as JSON ``` ## Limits and good practices - **No key, no sign-up**: the public content is open. Keys and test environments only exist for contracted integrations, agreed case by case. - **One request per second**: that's the crawl rate robots.txt asks for on the pages. Pages have no automatic blocking, and llms-full.txt gives you the whole site in a single request. The API has the limits described above. - **Attribution**: you're welcome to quote the content; please keep the MFactor name and a link to mfactor.dev in the attribution. - [Custom integrations](https://www.mfactor.dev/en/contact): a webhook, a dedicated API or a staging environment for a project of yours: get in touch through our contact channels. ## Frequently asked questions ### Do I need an API key to read the site's content? No. All public content and the v1 API are served without authentication: a GET is all it takes. The API states its rate limits on every response, in the RateLimit and RateLimit-Policy headers. Keys are only needed for contracted integrations, which we set up case by case through our sales team. ### How do I request the Markdown version of a page? Send the Accept: text/markdown header to the page's own URL. The response comes back with Content-Type: text/markdown; charset=utf-8 and Vary: Accept. If you'd rather use an explicit URL, add the .md suffix to the path, as in /en/services/mlabs.md. ### What happens if I ask for a format you don't serve? You get a 406 Not Acceptable, with a plain-text body listing the available representations. A path that doesn't exist returns 404, also with a short body pointing to the sitemap and the llms.txt. You never get a 200 with the app shell. ### Does MFactor have a documented API? Yes. The REST API lives at /api/v1 and the OpenAPI 3.1 spec is at /openapi.json, with an operationId, a description and typed JSON schemas for every operation; the RFC 9727 catalog at /.well-known/api-catalog points to it. The version goes in the path, breaking changes open a new version, and deprecation is announced through the Deprecation and Sunset headers at least six months in advance. Errors come back as JSON in the RFC 9457 format, with a stable code and a hint on how to fix it. ### Is there an official CLI? Yes, the @mfactor/cli package. It wraps the same HTTP calls in short commands, so you can script reading the content without writing any client code. The source code lives in the cli/ directory of the site's repository. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # About MFactor > We're a Brazilian technology company based in Leme, in the São Paulo countryside, building custom software, e-commerce, cloud infrastructure and applied artificial intelligence for clients all over the country. URL: https://www.mfactor.dev/en/about Site: MFactor (https://www.mfactor.dev) ## What we deliver - In-house team - Leme, SP, Brazil - Clients all over Brazil - From project to operations ## What we do MFactor started with a frustration anyone who has ever hired a tech vendor knows well: the vendor delivers the system, disappears, and the company is left with code nobody understands. That's why we built the operation around our own team, without outsourcing development. The people who build it are the people who support it afterward. Our work runs from the technical assessment to the system running in production. That includes designing the architecture, writing the code, setting up the infrastructure, monitoring what's live and improving the product as the client's business changes. We work with everyone from startups validating their first MVP to corporations with legacy systems and lots of integrations. ## The operation in numbers - **75,000+ nodes**: of infrastructure managed in production. - **35,000+ people**: reached by the platforms we've delivered. - **15+ industries**: served: healthcare, retail, agribusiness, manufacturing, education, financial services. - **7 service lines**: MLabs, MReach, MHost, M-AI, MRecovery, MPartner and MServices, with a single sales contact. ## How we work - **Assessment before the quote**: we get to know your operation before we put a number on anything. The assessment is free and you get the scope in writing. - **Iterative delivery**: you see the product working long before the project ends, in a staging environment that's live from the first few weeks. - **The code belongs to the client**: on custom projects, the repository and the documentation are handed over to you. You're never locked in to a vendor. - **Support from the people who built it**: post-launch support comes from the same team, not from an outsourced help desk that has to learn the project from scratch. ## Company details - **Name**: MFactor (also written as M-Factor and MFactor Tecnologia). - **Headquarters**: Leme, São Paulo, Brazil. We work remotely with clients all over Brazil. - **Languages**: we work in Portuguese, English and Spanish and reply in the language you wrote to us in. Technical documentation is available in English too. - **Official website**: mfactor.dev. Any other domain isn't ours. - [Where to see our work](https://www.mfactor.dev/en/showcase): a portfolio of projects delivered and running in production. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # Talk to MFactor > Three channels, all monitored by people on the technical team. You'll hear back within one business day, and the first assessment is free. URL: https://www.mfactor.dev/en/contact Site: MFactor (https://www.mfactor.dev) ## What we deliver - WhatsApp - Email - Form - Reply within 1 business day ## Official channels - [WhatsApp](https://wa.me/5519997789831): +55 (19) 99778-9831, the fastest way to start a conversation. - [Email](mailto:alexandre.martins@mfactor.dev): alexandre.martins@mfactor.dev, best when you already have a scope, attachments or documentation. - [Form](https://www.mfactor.dev/en#contato): the form on the home page goes straight to the sales inbox, with no middleman. - **Address**: Leme, São Paulo, Brazil. We work remotely, with in-person meetings arranged when the project calls for it. ## What happens after you write The first reply arrives within one business day and comes from someone who knows the subject, not a triage desk. We usually set up a thirty-minute call to understand your operation, the problem and the timeline. That call leads to a free technical assessment: what can be done, in what order and what the risks are. Only after that comes the quote, with the scope in writing, a timeline for each stage, and what is and isn't included. We don't pull numbers from a market average. ## What helps speed things up - **The problem, not the solution**: describing what's hurting the operation usually gets you further than asking for a specific technology. - **Systems involved**: ERP, CRM, payment gateway, spreadsheets: what already exists and needs to connect. - **Deadline and constraints**: a hard deadline, a rough budget or a regulatory requirement changes the proposal. - **Who decides**: knowing who signs off saves two weeks of conversations that go nowhere. ## For agencies and partners If you're an agency, studio or freelancer and want to resell development under your own brand, MPartner is the way to go: a standard confidentiality agreement, a cost sheet by project type, and we never contact your end client without your permission. - [MPartner](https://www.mfactor.dev/en/services/mpartner): white label for agencies, studios and freelancers. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # Technology in Leme and the São Paulo countryside > MFactor is a technology company based in Leme, in the São Paulo countryside. From here, with our own team, we build custom software, e-commerce, cloud infrastructure and artificial intelligence for companies in the region and all over Brazil. URL: https://www.mfactor.dev/en/leme-sp Site: MFactor (https://www.mfactor.dev) ## What we deliver - Based in Leme, SP - São Paulo countryside - Clients all over Brazil - In-house team ## A tech company from the countryside Leme is in the Piracicaba Metropolitan Region, between Pirassununga, Araras and Rio Claro, a little over an hour from Campinas. This is where MFactor works from: development, infrastructure and support all come from the same team, and we don't outsource the code. For a company in the countryside, that means a tech vendor that speaks the same language as your local operation and is still around after delivery, with the same team that built the system. ## Cities we serve in the region Leme and its neighboring cities: Pirassununga, Araras, Conchal, Santa Cruz da Conceição, Porto Ferreira, Rio Claro, Limeira, Cordeirópolis, Mogi Guaçu and Mogi Mirim. And the main hubs of the São Paulo countryside, such as Piracicaba, São Carlos, Araraquara, Campinas and Ribeirão Preto. That list isn't a limit. Most of MFactor's projects are run remotely, and we work with clients all over Brazil. ## What we do for companies in the São Paulo countryside - [Custom software](https://www.mfactor.dev/en/services/mlabs): internal systems, ERPs, CRMs and apps for the business rules no off-the-shelf tool covers. - [E-commerce](https://www.mfactor.dev/en/services/mreach): your own store connected to your ERP, your payment methods and your shipping carrier, so you can sell beyond your city. - [Cloud infrastructure](https://www.mfactor.dev/en/services/mhost): managed servers, Kubernetes and databases, with monitoring and high availability. - [Artificial intelligence](https://www.mfactor.dev/en/services/mai): agents and automations connected to the systems your company already uses. - [Fixing software built with AI](https://www.mfactor.dev/en/mrecovery): we repair websites, apps and systems that AI tools left buggy, slow or impossible for anyone to maintain. - [White label for agencies](https://www.mfactor.dev/en/services/mpartner): behind-the-scenes development for agencies in the region to resell under their own brand. ## How to reach MFactor - [WhatsApp](https://wa.me/5519997789831): +55 (19) 99778-9831, the fastest channel. - [Email](mailto:alexandre.martins@mfactor.dev): alexandre.martins@mfactor.dev, when there's an attachment or a written scope. - [Contact page](https://www.mfactor.dev/en/contact): the official channels and what to expect after you write. ## Frequently asked questions ### Is MFactor based in Leme? Yes. MFactor is based in Leme, in the São Paulo countryside, in the Piracicaba Metropolitan Region. Our development team is in-house and works from here for clients all over the country. ### Which cities in the São Paulo countryside do you serve? All of them. Leme and its neighboring cities, such as Pirassununga, Araras, Conchal, Santa Cruz da Conceição, Porto Ferreira, Rio Claro, Limeira, Cordeirópolis, Mogi Guaçu and Mogi Mirim, and the region's main hubs, such as Piracicaba, São Carlos, Araraquara, Campinas and Ribeirão Preto. We also work with clients in any other city in Brazil. ### Can a small business from the countryside hire MFactor? Yes. The first step is a free technical assessment, which tells you whether your case calls for custom software or whether an off-the-shelf product would do the job for less. When a subscription to a ready-made tool is enough, that's what we recommend. ### How does it work for companies in the region? The same way as for any client: the conversation starts on WhatsApp or by email, the assessment is free, the proposal comes in writing with scope and timeline, and the project is followed stage by stage until it's running in production. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil --- # Privacy policy > What data MFactor collects on this site, why it collects it, how long it keeps it and how you can ask for it to be deleted. Written for you to actually read, not to accept without reading. URL: https://www.mfactor.dev/en/privacy Site: MFactor (https://www.mfactor.dev) ## What we deliver - LGPD (Brazil's data protection law) - We don't sell data - Deletion on request - Named data controller ## Who the controller is MFactor, based in Leme, São Paulo, Brazil, is the controller of the personal data processed on this site, under Law No. 13,709/2018, Brazil's General Data Protection Law (Lei Geral de Proteção de Dados, or LGPD). Requests about personal data should be sent to alexandre.martins@mfactor.dev, which is also the address of our data protection officer. ## What data we collect - **Data you send us**: name, email, phone number, company and the message you write in the contact, quote and briefing forms. Only what you type. - **Browsing data**: pages visited, referral source, device type and campaign identifiers, collected by Google Analytics, Google Ads and Vercel Analytics. - **Technical data**: IP address and request headers, logged by the infrastructure for security and troubleshooting. - **Course area**: for people who sign up for the free courses: the login email and progress through the lessons, used only to give access to the content. ## Why we process this data Form data is processed to respond to your message and prepare proposals, on the legal basis of performance of a contract or of preliminary procedures related to a contract. Browsing data is processed on the basis of legitimate interest, to understand how the site and the campaigns are performing, always in aggregate form. We don't sell, rent or hand over personal data to third parties for marketing purposes. We don't use the data sent through the forms to train artificial intelligence models. ## Who we share it with - **Vercel**: site hosting and access logs. - **Supabase**: the database for the blog, the proposals and the course area. - **Google (Analytics and Ads)**: audience and campaign measurement. - **Email provider**: delivery of form messages to the sales inbox. ## How long we keep it Contact messages and proposals are kept for up to five years, in line with the civil statute of limitations and the need to keep a business record. Browsing data follows the standard retention period of the measurement tools, up to fourteen months. Course area data is kept for as long as the enrollment is active. ## Your rights - **Confirmation and access**: find out whether we process your data and get a copy of it. - **Correction**: ask us to update incomplete or out-of-date data. - **Deletion**: ask us to delete data processed on the basis of consent. - **Objection and portability**: object to a type of processing or ask for your data to be transferred to another provider. - **How to use these rights**: write to alexandre.martins@mfactor.dev. We reply within fifteen days. ## Cookies and changes The site uses measurement cookies from Google Analytics and Google Ads. On your first visit, a notice asks whether you accept them. Until you do, these cookies stay off (Google Consent Mode) and measurement happens without identifying your browser. To change your choice later, use the Cookies link in the footer. This policy may change when the site or the tools change. The current version is always the one published on this page, and we announce significant changes here before they take effect. ## Contact - WhatsApp: https://wa.me/5519997789831 (+55 (19) 99778-9831) - Email: alexandre.martins@mfactor.dev - Location: Leme, SP, Brazil