FAQ
Common questions about Anrixa projects.
These answers explain how Anrixa approaches AI software, websites, digital systems, contact forms, SEO, security-aware deployment, and product launch work.
Does Anrixa only build AI software?
No. AI software is one direction. Anrixa also builds digital systems, websites, internal tools, Android/product utilities, backend services, automation workflows, and brand-engineering structures.
Can Anrixa rebuild a website and fix SEO at the same time?
Yes. The stronger approach is to rebuild structure, content, metadata, schema, sitemap, internal links, contact flow, and deployment together. SEO cannot be separated from content and architecture.
Does the contact form need a backend?
Yes. A static form can open email, but real submission requires a backend. Anrixa’s own contact system uses a FastAPI endpoint, Nginx proxy, Zoho SMTP, message logging, and safe fallback behavior.
Can Anrixa work with existing servers?
Yes, if the server state is known. Deployment should include backups, Nginx testing, explicit document roots, and rollback discipline.
What should I send first?
Send the current site/app/server state, the target result, the problem you are trying to solve, and any constraints such as language, platform, security, app-store, or SEO requirements.
How the work is evaluated
Anrixa scopes this work around a concrete operating problem: who uses the system, what information enters it, what decisions it supports, what must be reviewed, and what should happen after launch. The first delivery target is not a decorative demo; it is a stable path from input to result.
Useful projects usually include a few visible checkpoints: a route map, data or content model, interface outline, backend or automation boundary, deployment plan, logging and backup approach, and a handover note. These checkpoints make the work easier to review before it becomes expensive to change.
Related pages explain the delivery path in more detail: the process page covers project shaping, pricing explains how scope affects cost, case studies show representative work, and the contact form collects enough context to define a practical first phase.
Additional practical questions
Why does Anrixa separate AI software from AI systems?
AI software is the visible product or workflow. AI systems include the supporting structure: data preparation, retrieval, review, validation, permissions, logs, and deployment. Separating them makes project scope clearer.
Can Anrixa improve an existing site instead of rebuilding everything?
Yes, if the current structure is recoverable. The first step is to inspect content, routing, server root, metadata, sitemap, contact flow, and deployment risk. Sometimes a patch is enough; sometimes the safer path is a controlled rebuild.
Why are Chinese pages not active yet?
Regional-language pages should not be published as weak automatic translations. They should be prepared after terminology, legal wording, local positioning, and service descriptions are reviewed.
What makes a project ready to start?
A project is ready when the goal, current state, users, constraints, materials, decision-maker, and expected output are clear enough to define a first delivery phase.