If you need to decide how permission boundaries, execution audit trails, local integration, or formal delivery should be handled, this page is more useful than another abstract discussion.
Lead Entry
Lead Routing & Contact
Founder SignalBefore submitting a lead, first decide whether you are closer to the free path, a beta application, formal team collaboration, or enterprise delivery.
If you already have one concrete automation problem, the beta page is usually the better first step. If you are already discussing delivery boundaries, deployment, or budget, use the formal lead path.
For enterprise automation, platform-style delivery, private deployment, and governance upgrades around existing scripts and workflows, this page currently routes free-path evaluation, local script-slot expansion, team-edition decisions, and enterprise consultation.
Free-path evaluationBeta applicationLocal script-slot expansionTeam-edition entryEnterprise / private deploymentLocal scripts, CLI, and templates
Apply for BetaSubmit a cooperation leadView service packagesView founder backgroundView Product OverviewView GitHub
The point is not to retell a broad platform story. The point is to clarify the next entry, the required preparation, and the first governed sample you should launch.
EXECFABRIC // CONTACT NODEOPEN
const leadEntry = ['free_line', 'local_slots', 'team_saas', 'enterprise_delivery']const contactMail = 'zmx2321@163.com'const focus = ['delivery', 'product', 'private deployment']
reply-window: async but stable
Follow-up is split into free-path evaluation, local script slots, team-edition qualification, and enterprise consultation instead of collapsing into one oversized project conversation from the beginning.
The script or workflow type, the expected number of users, and whether intranet, local execution, or private deployment is involved.
Good Fit
Scenarios worth discussing now
- Best for teams that already have scripts, scheduled jobs, file workflows, or local-bridge requirements
- Useful when you need to clarify execution traceability, result return, intranet access, or private-deployment boundaries
- Suitable when you want to decide how phase one should start and what environment or delivery inputs should be prepared
- Best when a real scenario should determine whether the standard path is enough or formal delivery is needed
Current Entry
The next step after the public experience entry
- You can already run the public experience flow first and feel one full "AI schedules a script" chain.
- If you want to keep onboarding scripts yourself, the next step is to register and enter the personal execution console.
- If you are still an individual user and have not entered formal collaboration yet, first decide whether you only need local script-slot expansion.
- If your focus is multi-user collaboration, permission audit, or local bridging, first determine whether the standard team edition is enough or whether this should move directly into enterprise delivery.
Before Contact
Information worth preparing before you reach out
- What kinds of scripts, workflows, or data tasks you want AI to orchestrate
- Whether you need multi-user collaboration, approval, permission control, or execution auditing
- Whether local environments, intranet resources, or private deployment are involved
- Whether you want to stay on the free path, expand personal space, move into the team edition, or discuss an enterprise plan immediately
Lead Split
Before submitting a lead, decide which category you belong to
| Your current state | Best-fit next step | Why | Suggested entry |
|---|---|---|---|
| You are touching the platform for the first time and only want to sense the product | Start with the free path | First confirm whether this is even worth understanding further. There is no need to jump into project discussion immediately. | Getting Started |
| You already have one very specific automation problem and want to validate it first | Apply for Beta first | A structured intake is a better way to judge fit, priority, and the right first step than a broad generic inquiry | Apply for Beta |
| You already connect scripts continuously in your personal space, but have not entered multi-user collaboration yet | First decide whether local script slots need expansion | This is lightweight personal expansion, not a formal team tenant | Membership & Pricing |
| You are preparing for multi-user collaboration, formal accounts, and a steadier usage cycle | Move into the team-edition monthly or annual entry first | The current standard team edition is handled through the shared-SaaS frontend, so the standard path and onboarding mode should be validated before anything custom | Billing & Membership / Tenant Payment Guide |
| You involve intranet deployment, local bridging, stronger isolation, or formal project acceptance | Go directly into enterprise / private-deployment discussion | The key questions here are deployment, delivery boundaries, and governance requirements, not a standard membership page | Service Packages / Deployment & Delivery Boundaries |
Direct Submit
Official-site beta / demand form
You can now submit the form directly on the official site. The lead goes straight into our backend public database instead of relying on email or a third-party form relay. If you already have one concrete problem, leave it here first.
Route Guide
What happens after you submit
- If you only want to feel the product first, you can still go to the free experience page.
- If you already have one concrete problem, this page is the fastest way to get it into the shared lead path.
- If you are already close to formal cooperation, start from the same form so the scenario lands in the same backend database.
- Script governance, local bridging, team collaboration, and enterprise delivery can all be routed from this one form.
What To Prepare
- Your company / role, or at least the context in which the problem appears.
- One specific automation problem, not a broad list of ideas.
- Your common scripting language and the weekly time cost.
- If local execution, intranet access, or private delivery is already known, mention that too.
First Message
Describe the highest-friction workflow first
It is usually more useful to explain the current task chain, its inputs and outputs, and how often it runs than to start with a broad team intro.
Decision
Judge whether step one is worth launching
The first stage should stay small and verifiable so everyone can confirm whether it really saves time before a larger second-stage scope opens up.
This official-site form now writes directly into our backend public lead database with page source and scenario fields attached.
Path 01
Personal experience / execution console
Let developers and individual users feel the value first at a lower threshold, then decide whether their own scripts should be formally onboarded.
Path 02
Personal continuation / local script slots
This fits people who already keep connecting scripts in their personal space but have not entered formal multi-user collaboration. The focus is personal slot expansion, not a rebrand into the formal team edition.
Path 03
Team-edition SaaS
This path takes multi-user collaboration, shared execution capability, approval, permission control, and a more stable formal-team model. It currently goes first through the standard SaaS formal-tenant entry for registration or demo handled by the shared-SaaS frontend. Stronger isolation or deeper customization can later move into enterprise / private deployment.
Path 04
Enterprise / private deployment
This path takes stronger isolation, higher security requirements, intranet environments, local Agent needs, and formal delivery constraints.
Current Cooperation
Cooperation types that are best to discuss first right now
- Turn one repetitive process into a minimal automation delivery first
- Bring existing Python scripts or Skills into a unified execution entry
- Run pilots, formal delivery, and lightweight private deployment for the team and enterprise editions
- Help determine whether the shared-SaaS tenant path is enough or whether the work should move directly into enterprise delivery
- Local scripts, CLI, local-environment bridging, and governed execution strategies
How To Start
The most recommended way to start
- Bring the most painful, most repetitive, and most rule-bounded process first
- Start by narrowing the scope to one point instead of opening a large all-in project immediately
- Run the first step through, then decide whether the second stage is worth expanding
- If you are still unsure whether the work is worth doing, start with the smallest possible assessment
Founder Background
Delivery background and public materials
- The long-running mainline has been frontend engineering, GIS visualization, and government / enterprise delivery.
- Over the last two years, the work has continued to deepen in Python automation, data processing, and small-to-medium backend support.
- ExecFabric is not being built as a broad AI story. The goal is to make script onboarding, permission boundaries, execution audit trails, and local bridging into a deliverable product.
Public Proof
What is publicly visible today
- Public GitHub repositories and project structure
- Project notes and reflections in the blog
- Public explanations of the product, delivery, and service packages on the docs site
- The continuously updated ExecFabric docs and frontend entries
Channels
Backup contact channels and public entry points
Product Entryexecfabric.cn
Use the login / register entry or the free experience page to submit the demand directly into the shared database flow.
GitHubzmx2321See public repositories, coding style, and delivery maturity.
Docs Repoexec-fabric-ai-skill-platform-docSee the docs-site pages, styling, and deployment configuration directly.
Blogvite-blogContinue with project notes, thinking, and public writing.
Next Read
Continue with platform and delivery materials
Continue with Product Overview, the CLI & Local Agent Guide, Capabilities, and Version Stages & Upgrade Path, then enter the conversation with a concrete question.