forculus-labs/forculus

Make an app on Forculus identify its caller properly, by verifying the identity token with the SDK. Use when an app needs to know who is using it, show a name, or allow some people more than others.

Give a bot, script or other agent its own identity on Forculus, grant it apps, and take them away. Use when the user wants an automated caller named in the audit log, or asks to revoke one.

Give an app on Forculus a key-value store or a queue for background work (emails, imports, reports, caches), and handle the queue's deliveries safely. Use when an app needs fast key-value reads, a cache, or work done outside a request.

Read or change what an app on Forculus stores, its files and its database, export it, or put it back as it was. Use when the user asks what's in an app's database or files, wants to fix or import data, back it up, or undo a change.

Work out why an app on Forculus is failing, refusing people, or serving the wrong version. Use when a deploy went wrong, someone can't get in, or the app is returning an error.

Deploy what was built in this project to Forculus, check it answers, and share it. Use when the user asks to deploy, ship, host, publish or share an app from this project.

Put an app on Forculus at a domain the user owns, like tools.example.com, and check its DNS. Use when the user wants an app on their own domain or a custom domain isn't working.

Move an app to Forculus from Vercel, Netlify, Replit, Lovable, Bolt, v0 or any git repository, with its variables, keys and scheduled jobs. Use when the user asks to import, migrate or move an app here from another host.

Answer who uses a workspace's apps on Forculus, how often, which apps nobody opens any more and which ones lost their owner. Use when someone asks about adoption, usage, active people, unused or abandoned apps, or an app's audience.

Run an app locally with Forculus's sign-in in front of it, so identity works the same as in production, as an owner, editor, viewer, agent, bypass token, scheduled job, webhook or someone the app isn't shared with. Use when developing or testing an app that verifies its caller, checking what each role sees, or when something works locally but not deployed.

Control which hosts an app on Forculus may send requests to, and let it use the workspace's AI provider keys (Anthropic, OpenAI, Gemini, Mistral, Groq, Cohere, Azure OpenAI or Amazon Bedrock) within a monthly budget. Use when the user wants to lock an app down to the services it needs, an outbound request is refused, or an app needs an AI provider.

Use a Postgres database the person already has (Neon, Supabase, RDS or any other the internet can reach) from an app on Forculus, without its password in the app. Use when an app needs Postgres, or the person gives you a postgres:// URL.

Put a change up at a preview address of its own on Forculus, leave the live version alone, and put the preview live once it's approved. Use when the user wants to try a change before it goes live, or show it to someone first.

Run a path on an app on Forculus on a schedule, like a nightly job or an hourly sync, and check or pause those jobs. Use when the user wants something to happen every day, hour or week, or asks why a job didn't run.

Give or take away access to an app on Forculus, for a person, everyone at a domain, a group or the whole workspace, and answer requests for access. Use when the user asks to share an app, add someone, change a role, revoke access, or deal with access requests.

Make a new app on Forculus from nothing, starting from a template, and deploy it. Use when the user asks for a new app, site, page, tool or API and there's no code for it yet, for example "make me a page for the team" or "build a small tool to track orders".

Let a third party (Stripe, GitHub, Slack, Shopify, a Standard Webhooks sender such as Resend, or anything that signs with HMAC-SHA256) deliver webhooks to one path of an app on Forculus, with Forculus checking each signature. Use when an app needs to receive a webhook or callback.