inAiLoading page content...
inAiinAiLoading page content...
Clear answers about inAi, our products, AGI, Open Source, AI for Everybody, Trust, and how to work with us.
inAi is an AI-native product company building for the intelligence / agent era. This FAQ explains the public architecture of the website: what we build, how our product categories work, how we think about AGI and Research, what Open Source means at inAi, and how to contact or work with us.
inAi is an AI-native product company bringing AI into real-world software, work, personal workflows, agent systems, client-specific systems, and open ecosystems. The company works across Business, Consumers, Agents, Services, and Open Source.
It means moving AI from demos and isolated chat experiences into products, tools, workflows, systems, agents, industries, personal work, and open ecosystems.
AI-native means products are designed around AI as a core operating layer from the beginning, not added as a small feature later. Product company means inAi builds products, not just consulting, research, or agency work.
AI is becoming a broad operating layer for software and work. inAi uses product categories so that breadth is structured rather than random.
AI in the Real World is the Mission page. It explains what inAi is trying to achieve and why the company exists.
inAi has European company and legal context, with formal company information in Legal. The public mission is broader: AI-native products for the real world.
inAi organizes public product and service directions around Business, Consumers, Agents, Services, and Open Source. PageMind is the current Business product, Emplo is the current Consumer product, Products for Agents covers software for agents to use, Services covers custom AI work for specific client problems, and Open Source presents selected public tools.
Top navigation shows the company architecture. PageMind and Emplo are product pages inside categories, not top-level company labels.
They are current products in two categories, but they are not the whole company. PageMind belongs under Business, Emplo belongs under Consumers, and inAi is broader than either product.
Labels such as private beta, pre-launch, active, experimental, reference, legacy, research, and stance explain current status. They prevent false maturity claims without shrinking ambition.
Some AI needs can be served by products. Others need direct work: understanding the problem, designing the right system, preparing data, building the application, integrating it into existing tools, and supporting it after launch.
AI Services are for clients who need more than advice and more than a generic chatbot. The right fit is a real problem that needs diagnosis, design, execution, integration, and support.
Custom AI work should be clear before it is built, private by default, scoped before development, evaluated against real use, delivered with an agreed operating path, and supported after launch where support is part of the project.
Client work is confidential by default. Services projects may involve private documents, product plans, operational processes, business data, internal tools, users, datasets, source materials, or unreleased product ideas. inAi does not treat those materials as public proof.
PageMind is inAi's current Business product. It supports retail, product data, catalog, and compliance-support workflows by helping transform supplier and product inputs into structured catalog-ready outputs with traceability and review.
PageMind should be read through the current PageMind page. It is not presented here as public self-serve software; access and pilots are handled through the product and contact routes.
Use the PageMind page or Contact route for PageMind pilot requests. Companies can also use Pilots / Corporate partners when the discussion is broader than one product request.
No. PageMind can support compliance-related product-data workflows through structuring, traceability, and review, but it is not legal advice and does not guarantee legal compliance.
Use the current PageMind page as the source for supported inputs and outputs. The FAQ should not invent new file formats, connectors, exports, or roadmap promises.
Emplo is inAi's AI career agent for job seekers. It belongs under Consumer Products because it is built for individuals and personal career workflows.
Emplo should be read through the current Emplo page. The FAQ does not present Emplo as a public launch unless the product page does.
Use the Emplo page or the Contact route for Emplo waitlist interest. Joining a waitlist does not guarantee access or a specific response time.
No. Emplo is positioned for job seekers, not as recruiter software or an employer applicant-tracking product.
No. Emplo supports job seekers, but it does not guarantee a job, interview, salary, offer, or hiring outcome.
Emplo should not be read as uncontrolled auto-apply or spam automation. Career workflows need user control, supervision, and approval where sensitive.
It means software that AI agents can discover, understand, call, and use: tools, interfaces, workflows, memory systems, code systems, documentation, protocols, and operating surfaces built for agents as software operators.
No. Products for Agents means software for AI agents to use, not agents sold by inAi.
Humans use screens, buttons, menus, and dashboards. Agents need callable tools, structured actions, documentation, state, memory, permissions, predictable outputs, and recovery paths.
Agent-ready software provides meaningful end-to-end use by an agent or agent-controlled workflow, with tool surfaces, structured inputs and outputs, agent-readable documentation, state, recovery paths, and review or permissions where needed.
AGI as a System explains inAi's stance on general intelligence. Products for Agents explains the product and software layer for a world where agents operate software.
Open Source is one of inAi's four product categories. It presents selected public tools, experiments, utilities, and reference projects released in the open.
The public portfolio includes PatchBay, PrismOS, ImageAI Batch Generator, WhisperMind, AdditionalApps, ChainerAI, and ChatGPT Assistants UI.
Status labels such as Active, Experimental Prototype, Experimental, Reference Utility, Legacy Prototype, and Legacy tell visitors how to interpret each repository.
Repository-specific contributions happen through GitHub where available. Broader contribution interest can go through Contributions or Contact, without implying a formal contribution program exists for every project.
Each repository has its own license. Check the license file in the relevant GitHub repository; the FAQ does not create a blanket commercial-use rule.
No. inAi releases selected tools publicly, but private product internals, customer data, security-sensitive systems, and internal architecture are not public.
AGI as a System is a public stance page. It argues that general intelligence may emerge from systems of models, agents, tools, memory, perception, execution, coordination, feedback, and environment.
No. AGI as a System is a research and stance page, not a claim that inAi has AGI, sells AGI, or solved AGI.
The four research directions are Limits of Intelligence, Agentic Decision Systems, AI for Knowledge Creation, and AI and Business Operations.
Research informs products where the connection is real. The FAQ should not pretend every research idea is already a mature product.
AI for Everybody is inAi's public explanation hub for AI, agents, work, risk, AGI, and the intelligence era. It is written for broad audiences without unnecessary complexity.
It is for teenagers, adults, older readers, workers, students, business people, skeptical visitors, and nontechnical readers who need clear explanations of AI.
Yes. It should address myths, stereotypes, jobs, safety, privacy, misinformation, regulation, energy, hallucination, agents, and AGI where relevant, with a cautiously positive and grounded tone.
Trust is inAi's credibility page. It explains how inAi builds, how product maturity is communicated, and where to find Legal, Privacy, Open Source, Research, and Mission information.
Different products need different levels of freedom, review, and control. Intelligence can be free where freedom creates value and controlled where control creates trust.
Use Legal and Privacy as the formal source. This FAQ keeps privacy answers short and does not invent technical, hosting, security, GDPR, deletion, or support claims.
Legal and Privacy documents remain in the Legal area. Trust links to them, but Legal remains the formal source.
Use Contact to choose the right route: general message, product access, PageMind pilot, Emplo waitlist, testers, bug report, problem report, complaint, investing, work, internship, research, grants, government, Open Source, contributions, or partnerships.
Partners is a routing hub for Work with us, Investors, Academia / Research, Internships, Contributions, Testers, Grants, Government / Public institutions, and Pilots / Corporate partners.
Start with Partners if you are choosing a collaboration path, or Contact if your request is already specific. Serious routes include research, pilots, grants, public institutions, investors, contributors, testers, and work.
Use PageMind for PageMind pilot interest, Emplo for Emplo waitlist interest, or Contact when you need a single routing page. Access is not guaranteed.
Use Contributions for broader contribution interest, GitHub for repository-specific Open Source work where available, and Testers for structured feedback. These routes do not guarantee acceptance.
Use Contact to choose the right path: product access, pilots, waitlists, testing, partnerships, internships, grants, research collaboration, Open Source contributions, bug reports, complaints, or general messages.
